Higher Logic Informz and ActiveCampaign are separate email marketing connections. Each connection lets Rhythm send saved queries to that platform as targeted lists.
This article explains how to connect or update either connection. After you connect, you send contact lists by integrating a saved query in the application where that query lives. The send is one-way: Rhythm sends your data out, but it does not bring delivery, open, click, bounce, or unsubscribe results back from either platform.
Prerequisites
- For Informz: the brand name, brand identifier, username, and push key from Higher Logic.
- For ActiveCampaign: the developer key and host address from your ActiveCampaign account's Developer settings, plus a default sender address and the short reminder sentence ActiveCampaign requires on every list.
- Access to System & Security in the Console. You do not need a separate permission for either connection.
- Your Rhythm account must be enabled for the integration you want to connect. If the connection screen or catalog says it is not set up, contact your customer success manager.
- For Informz: access to your organization's Informz account, or to someone who has it. Setup, reconnection, and troubleshooting often require a matching change in Informz.
Connect Higher Logic Informz
- Go to System & Security › Integrations, then choose the Higher Logic Informz card.
- Choose
Create Informz Account. - Enter a connection name. You will see this name later when you choose where to send an integrated query.
- To receive a notification each time a list sync finishes, enter an email address.
- Enter the brand name, brand identifier, push key, and username Higher Logic gave you. Higher Logic provides and manages these values; Rhythm only stores what you enter. If you need to change the encryption key, arrange that with Higher Logic first, then enter the new key here.
- Choose
Save Changes.
Result
Rhythm saves the connection so it can receive integrated queries. Rhythm syncs each list with Informz about once an hour. If you entered a notification email, Rhythm sends a detailed sync-result message for every list so you can confirm what was sent.
Allow Rhythm's Addresses in Informz
Before Rhythm can push data to Informz, allow these addresses in the Informz console under Settings, System Settings, Informz API Configuration:
- Starting IP 3.232.5.78, Ending IP 3.232.5.78
- Starting IP 44.208.186.1, Ending IP 44.208.186.1
- Starting IP 52.6.113.37, Ending IP 52.6.113.37
Rhythm cannot confirm whether this step is complete, so check it first if your pushes never appear in Informz. If pushes still do not arrive, contact Support and include why you need help and any error message or screenshot you have seen.
Reconnecting an Existing Informz License
If your organization already has an active Informz license and needs to reconnect it, you usually only need to update the brand, key, or username on the existing connection in Rhythm, with no additional Rhythm fee. Reconnecting restores the existing authentication between the two systems; it does not add new functionality. If you are not sure whether you are reconnecting an existing license or adding new capability, confirm pricing with your customer success manager before assuming there is no added cost.
In some cases, updating the connection in Rhythm is not enough to restore syncing. If lists still are not updating after you save, check for a setup step inside your Informz account, and contact Support if you cannot find one.
Connect ActiveCampaign
- Go to System & Security › Integrations, then choose the Active Campaign card.
- Choose
Create Active Campaign Setting. - Enter a connection name.
- Enter the developer key and host address from ActiveCampaign under Settings, Developer.
- Enter a default sender address and a default sender reminder, which is the short sentence ActiveCampaign shows recipients to explain why they received the email.
- Turn on
Enable Connection:when you are ready for the connection to run. - Choose
Save Changes.
Result
Rhythm saves the connection so it can receive integrated queries. ActiveCampaign lists sync on the same roughly hourly schedule as Informz.
Query Requirements for a Sent List
Not every saved query can create a list on either platform.
- The query's primary target must be contacts, not another record type such as orders or invoices, even if the results include a contact email field. A query built around orders or invoices does not work for these integrations, even when it includes contact fields in its results.
- The query must return individual contact-level records and include the Email Address - Contact field. Informz uses that field to decide which address to send to; if the field is missing, contacts are not passed through as subscribers even when other email fields are in the query.
- You can add other email-address fields to the query, and Rhythm sends them to Informz as custom fields you can use in your templates. Only the contact's primary email address is mapped as the subscriber Email field; the integration does not guess which alternate field to use instead.
- Contacts also need an email address and must be eligible for email marketing. Filtering by active contact status, not opted out, and a non-blank email address keeps the list aligned with who can actually be reached, since the destination is an email marketing platform.
- If the query's own criteria becomes invalid — for example, because it references a custom contact field that was later deleted — the query stops running, and the list it drives stops syncing until you remove or correct that criterion. The list resumes on the next hourly sync after the query works again. This applies to both Informz and ActiveCampaign.
- Not every query or report-builder pattern is guaranteed to work with an integration. Some specialized query types may need additional support on the integration's side before they can be sent; if a query consistently fails to sync while simpler queries succeed, that may be the reason.
- Rhythm never sends an empty list. If a query returns no contacts, Informz rejects an empty upload, so Rhythm skips that send until the query returns results again.
Tip
If someone else needs to maintain an integrated query, reassign the query's ownership instead of recreating it. The integration depends on the query's existing identity; recreating the query under a new name breaks the link to the list it was feeding.
How Your List Appears in the Other Platform
Rhythm sends the saved query's name as the list or interest name on the destination platform. Give your query a clear, descriptive name without unusual special characters, because Informz can reject or mishandle a name it does not recognize.
After you integrate a query, Rhythm sends its results to Informz as a target group. Rhythm creates that target group from the query, so it does not need to already exist in Informz. The first time an integrated query reaches Informz this way, expect a notification email from Higher Logic confirming it.
Informz may use its own mapping to decide which folder or interest area receives the list, and that mapping is not visible from Rhythm. If a list appears somewhere you did not expect, check its interest or folder assignment in Informz rather than in Rhythm.
Each sync sends the complete, current list. Informz replaces a group's membership with exactly what that sync contains, so if a sync temporarily contains only a few rows, those rows replace the rest of the group instead of being added to it.
If you move an Informz template from a standard mailing into a Campaign, the merge fields available to it can change. Check with Higher Logic if fields you expect stop working after that kind of move.
Informz applies its own suppression rules and removes duplicate or previously unsubscribed addresses, so the subscriber count in Informz can be lower than your query's result count. A single invalid or mistyped email address does not stop the rest of the list from sending.
If a welcome or other membership email is sent from Informz rather than from Rhythm, edit its content in Informz. Rhythm does not store that message, even though the email relates to a Rhythm membership event.
Settings
| Setting | Where | Options | Effect |
|---|---|---|---|
| Connection name | Both | Text, required | Names the connection when you choose where to send an integrated query |
| Brand name, brand identifier, push key, username | Informz | Text, all required | Uses the credentials Higher Logic issued for your Informz account |
| Notification email | Informz | Email address, optional | Sends a detailed sync-result message each time a list sync finishes, so you can confirm what was sent |
| Developer key, host address | ActiveCampaign | Text, both required | Uses the credentials from your ActiveCampaign account |
| Default sender address | ActiveCampaign | Text, required | Sends the sender value to ActiveCampaign when a list is created |
| Default sender reminder | ActiveCampaign | Text, required | Provides the explanatory sentence ActiveCampaign shows recipients |
Enable Connection: | ActiveCampaign | On or off | Controls whether the connection is active; an Informz connection has no equivalent switch and is always treated as on |
Change an Existing Connection
Open either list from the catalog, then select the connection's row to edit it. The form shows the credentials you entered before, including the key, so you can confirm they are still correct or replace them. You can also change any other setting. Save your changes to apply them.
For Informz, the username must belong to a real, valid user in the Informz console. Informz uses that user to authorize every API-driven change Rhythm makes on its behalf. You do not need a dedicated, Rhythm-only user; any valid Informz user works. You can switch to a different user at any time by updating the username here and saving, with no expected issues as long as the new user is valid in Informz. If the configured user later becomes invalid, loses permissions, or has an invalid email address in Informz, syncing can fail even though the rest of the connection looks correct. An incorrect username alone can also block syncing, even when every other field looks right.
For ActiveCampaign, you can reopen the connection at any time to confirm or replace the stored developer key. The ActiveCampaign user who generated that key also needs permission to retrieve lists in ActiveCampaign. If lists stop syncing even though the connection looks correct, check that permission in ActiveCampaign before assuming the key itself is wrong. If checking both the key and the user's access does not resolve the issue, contact ActiveCampaign support.
Dependencies and Precedence
Informz syncs hourly whether or not you enter a notification email. The email address only controls whether you receive a message about each sync; it does not control whether the sync runs. For ActiveCampaign, the sender address and reminder sentence apply to every list ActiveCampaign creates from this connection. You do not set them separately for each list.
Each list syncs on its own. One list failing to update does not mean every list, or the connection as a whole, has stopped.
An Informz list can also become paused. If a list's updates stop and nothing about its query changed, contact Support; the list may need to be pushed manually to resume.
If Rhythm's saved-query results are temporarily disrupted, any integration that depends on those queries can sync stale or missing data until query updates resume.
Informz updates only your organization's main account. Rhythm cannot route query results to a separate child or chapter account under that Informz account.
If a List Stops Syncing
| Symptom | Likely Cause | What To Do |
|---|---|---|
| A specific list stopped updating | Its saved query now has invalid criteria, often because it references a custom field that was later deleted | Open the query, remove or fix the invalid criterion, and save. The list syncs again on the next hourly run |
| Several or all lists stopped updating at once | In some cases, one failing query in your account has been enough to stop every other list from being sent until it was fixed | Check your integrated queries for one that recently changed or now returns an error, and correct it |
| ActiveCampaign returns an authorization error, or contacts silently stop arriving | The configured developer key is wrong, or the ActiveCampaign user who generated it lacks permission to access lists | Confirm the developer key in Rhythm, then confirm in ActiveCampaign that the key's user can retrieve lists. Contact ActiveCampaign support if both check out |
| ActiveCampaign shows as connected, but nothing has synced in a long time even though nothing changed | In some cases, processing for your account can stop without changing the connection's status | Contact Support so they can check whether your sync needs to be restored |
| Only some integrated queries fail to sync, even though the connection is already working | The data Rhythm sends for that specific list may not match what Informz expects | Contact Support so they can review the request Rhythm sent for that list |
| Logs or a status message show a successful send, but the list still hasn't updated | A specific query is timing out during the sync, even though the send itself succeeded | Simplify or correct the slow query. The list resyncs about an hour after the query is fixed |
| A query returns zero contacts | This usually reflects the query's own logic or criteria, not a broken sync | Check the query's results directly; the same audience built a different way may return contacts as expected |
| A query meets the requirements above and still doesn't appear as a list | The cause is not always visible from Rhythm | Contact Support with the query name and what you have already checked |
| A list syncs, but the platform shows fewer subscribers than your query's result count | The platform's own suppression rules, or duplicate and previously unsubscribed addresses, reduced the count | This is expected; a single invalid address does not stop the rest of the list from sending |
| A sync stops without any change on your part | The interruption may be on Rhythm's or the provider's side rather than your configuration | Wait for the next scheduled sync, and contact Support if it does not resume |
| Individual record updates keep reaching Higher Logic, but a full list sync is missing | In some cases, this reflects a provider-side processing issue rather than a Rhythm-side change | Contact Support if it persists across more than one sync |
| A send to Higher Logic succeeds, but the data doesn't appear right away | Higher Logic may still be processing it on their end | Allow extra time before contacting Support, since Rhythm cannot see Higher Logic's internal processing |
To test a fix without waiting on a full list, rebuild the failing query as a copy and confirm the copy syncs correctly before changing the original. To isolate a stubborn problem, try simplifying the query, recreating the same logic in a different application, or resaving a single contact record and checking whether it reaches the platform on the next scheduled sync.
When you contact Support about a sync problem, include the reason for your request and any error message or screenshot you are seeing. This helps Support review it faster.
Diagnosing Merge-Field and Data Problems
If a merge field or personalization token in a template appears blank, shows the wrong data type, or appears literally instead of being replaced, start by identifying the exact Rhythm form or query that produced that record. Review the merge-field configuration there, then compare the same form or query setup in another environment — for example, your sandbox against your live account — to see whether the problem repeats.
Comparing the query's raw output to the data Rhythm sends can show whether a field was dropped before or during delivery, which helps you separate a query problem from a delivery problem.
An error mentioning unparsable or non-parsable characters usually points to a malformed value in one of the mapped fields, often an email address. Fixing the one obvious bad value may not resolve everything if another field also has a stray character.
If a field pulled in from another application's query arrives under an unexpected name or does not populate, confirm it is mapped from the contact's primary email address rather than a differently named copy created inside that other query.
Change Impact and How to Revert
The Console does not offer a way to remove an Informz or ActiveCampaign connection from either list. To change a connection, open it, edit the fields you need, and save. The new values replace the previous values.
Permissions
Anyone who can sign in to the Console and open System & Security can view and change either connection, including its stored key. There is no separate permission for either connection.
Validation and Errors
For Informz, the brand name, brand identifier, push key, and username are required. For ActiveCampaign, the connection name, developer key, host address, default sender address, and default sender reminder are required. Save Changes will not complete the save until every required field on the form you are using has a value.
An ActiveCampaign developer key inherits the permissions of the ActiveCampaign user who generated it. If that connection later fails to retrieve lists or manage campaigns, even though the host address and developer key are both saved correctly, ask ActiveCampaign to check whether the user who generated the key has administrative or feature-level rights there. A key from a user without those rights can save successfully in Rhythm and still be refused by ActiveCampaign.