Site Messages: Difference between revisions
ContentBot (talk | contribs) (Created page with "```mediawiki = Site Messages = == Troubleshooting site messages == *Last updated March 17, 2025 at 6:02 PM* There are a few things that can prevent a site message from appearing for a contact. In this article, you’ll learn about the most common reasons why a site message may not appear, and how you can troubleshoot the issue. === Site tracking code was not installed on the exact pages where the site message will appear === In order for site messages to appear for...") |
(No difference)
|
Latest revision as of 18:41, 6 November 2025
```mediawiki
Site Messages[edit | edit source]
Troubleshooting site messages[edit | edit source]
- Last updated March 17, 2025 at 6:02 PM*
There are a few things that can prevent a site message from appearing for a contact. In this article, you’ll learn about the most common reasons why a site message may not appear, and how you can troubleshoot the issue.
Site tracking code was not installed on the exact pages where the site message will appear[edit | edit source]
In order for site messages to appear for your contacts, you need to install site tracking code on the exact pages that will display your site messages. To learn how to install site tracking on your site, see Installing site tracking.
In addition, you'll need to double check that the “Send Site Message” step in your automation reflects the correct URL.
Contact did not yet reach the “Send Site Message” step in your automation[edit | edit source]
Site messages will only appear for contacts that: 1. Have reached the “Send Site Message” step in your automation. 2. Have a tracking cookie associated with their profile (see next item for more information).
If a “Send Site Message” step was added to your automation AFTER a contact went through the steps that follow your site message step, they will not see your site message. To learn how to see your contact’s path in an automation, see Viewing contact paths in automation.
Contacts do not have a tracking cookie associated with their profile[edit | edit source]
In order to match page visits with contacts, one of the following must occur:
- Contacts need to submit an ActiveCampaign form. Note that the page they redirect to once the form is submitted must have site tracking code installed.
- Contacts need to click on a link in a campaign or automation email that takes them to a page with site tracking code installed.
- You can insert a contact’s email address into the site tracking code if you have already identified them by their email address.
If none of the three options outlined above occur, we are not able to match a page visit with your contacts and the site message will not appear.
Testing your site messages[edit | edit source]
In general, we recommend testing your site tracking and site messages before adding contacts to your automation. To test these two items, follow the steps below:
1. Submit a test contact to an ActiveCampaign form. This will allow us to apply a tracking cookie to that contact. Note that the page they redirect to once the form is submitted must have site tracking code installed. 2. Visit the page in which you will have the site message display. Then, go to the contact profile page for your test contact to see if the page visit was logged. It should appear under the “Recent Activities” stream. If not, double check to see if the correct domain was whitelisted and that site tracking code was installed on your site. 3. Add your test contact to the automation. You can add them directly from their contact profile page by clicking the “Add” button located in the Automations row, then clicking the checkbox next to the name of the automation containing your site messages.
If your automation has any wait steps that precede the "Send a site message" step, you can skip them.
Once you reach the “Send a Site Message” step, navigate to the page containing your site message. If it appears, you’re all set! If not, check out the troubleshooting steps above. If you still cannot see the issue, contact our Customer Experience Team and one of our specialists can assist you.
See Also[edit | edit source]
```