Editing Troubleshoot why automations are not triggered by web site visits

```mediawiki
'''Navigation:''' [[Main_Page]] > [[Automation]] > [[Troubleshooting]] > Troubleshoot why automations are not triggered by web site visits

== Troubleshoot why automations are not triggered by web site visits ==

ActiveCampaign allows users to automate communications based on various triggers, one of which is the '''Web page is visited''' trigger. This feature is crucial as it enables businesses to respond in real-time based on user interactions with their websites. However, sometimes these triggers may not function as intended. This article aims to help users understand common reasons why automations may not be triggered by web site visits and provides actionable troubleshooting steps.

== Introduction ==
The ability to automate responses based on web page visits is essential for creating personalized customer experiences. When set up correctly, the '''Web page is visited''' trigger can initiate an automation sequence whenever a contact visits a specified page on a website. If users experience issues where automations do not trigger as expected, it can impact engagement and conversion rates. This guide outlines common issues and solutions related to this functionality.

== How to Access This Feature ==
To access and utilize the '''Web page is visited''' trigger in ActiveCampaign, you must first set up site tracking in your account. Here’s how to access it:

1. Log in to your ActiveCampaign account.
2. Click on the '''Website''' option in the left menu.
3. Navigate to '''Site Tracking'''. 
4. Ensure that your domains are properly whitelisted.

Once site tracking is established, you can create or edit automations to include the '''Web page is visited''' trigger.

== Step-by-Step Instructions ==
To troubleshoot why automations are not triggered by web site visits, follow these detailed steps:

=== Check Domain Match ===
1. **Review the Domain in the Automation Trigger:**
   - Navigate to '''Automations''' from the left menu.
   - Select the automation you want to inspect and click '''Edit'''.
   - Click on the '''Web page is visited''' trigger to view the URL you have configured.

2. **Compare with Actual Domain:**
   - Ensure that the domain listed in your trigger matches the domain that contacts are actually visiting. 

3. **Fix Domain Issues:**
   - If there is a mismatch, update the domain in the trigger settings and ensure it includes a forward slash (/) at the end, if necessary.

=== Confirm Whitelisted Domains ===
1. Go back to the '''Website''' >> '''Site Tracking''' section.
2. In the '''Whitelist and Install Code''' box, check if the domain being visited is listed.
3. If the domain is absent:
   - Enter it in the '''Add Website URL''' field and click '''Add'''.

=== Validate the Trigger URL ===
1. Under the same automation, recheck the URL in the trigger configuration.
2. Confirm that it is correctly inputted and reflects the exact page URLs visitors are accessing. Using the example, ensure that both the root domain and any specific pages are accurately listed.

=== Implement Wildcard URLs ===
If your automation needs to cover multiple pages, consider using wildcard URLs:
- You can configure a wildcard URL such as '''yourdomain.com/blog/*''' to trigger the automation for any page under the blog section. This flexibility can increase the chances of successful triggering for different relevant pages.

== Configuration Options and Settings ==
When configuring the '''Web page is visited''' trigger, consider the following options:

- **Wildcards**: Use '''wildcard URLs''' to create broader triggers for multiple related pages.
- **Specific Page URLs**: Ensure that any specific page URLs in the automation trigger include the necessary forward slashes (/) and are correctly formatted.
- **Whitelisted Domains**: Keep track of all domains you have whitelisted to avoid mismatches.

== Best Practices and Tips ==
- Always test your automations after setting them up to ensure they trigger as expected.
- Regularly review and update your whitelisted domains to reflect any changes in your website’s structure.
- Use the '''Automations Overview''' to monitor the performance and efficiency of your triggers and make adjustments where necessary.
- Keep documentation handy for any changes made on your site that might affect triggers.

== Common Use Cases with Examples ==
- **E-commerce Engagement**: Trigger a welcome series for new visitors who check specific product pages.
- **Content Marketing**: Automate follow-up emails to contacts who read blog posts on specific topics.
- **Lead Nurturing**: Set up a series of emails for contacts who explore your landing pages or trial offers.

== Troubleshooting Section ==
If automations still fail to trigger after following the steps outlined:
- Recheck each configuration setting for typos or omissions.
- Review recent changes made to your website which might have altered URL structures.
- Ensure there are no restrictions on JavaScript or cookies that could affect tracking functionality.

== FAQ ==
=== Q1: What should I do if my automation is still not triggering after checking all settings? ===
A1: Double-check your domain whitelisting and confirm that the URL formats are correct. If you continue to face issues, consider reaching out to ActiveCampaign support.

=== Q2: Can I use multiple domains for tracking on a single automation? ===
A2: Yes, but all domains need to be whitelisted individually in the Site Tracking settings.

=== Q3: What are wildcard URLs and how do I use them? ===
A3: Wildcard URLs allow you to trigger automations based on multiple related pages by using the * symbol. For example, '''yourdomain.com/blog/*''' triggers whenever any blog post is accessed.

=== Q4: Will using wildcards impact automation performance? ===
A4: Wildcards can enhance performance by grouping relevant pages, but if overused could create excessive entries; always monitor the results.

=== Q5: What if the URL structure of my website changes? ===
A5: You will need to revisit your automation settings and update the trigger URLs accordingly.

=== Q6: Can I delete a whitelisted domain if it’s no longer in use? ===
A6: Yes, you can remove any domain that you no longer need listed in your whitelist.

=== Q7: Is there a limit to the number of wildcards I can use? ===
A7: There is no explicit limit, but using too many can lead to complexity in managing your automations. Aim for clarity and efficiency in your configurations.

By following this comprehensive guide, users can effectively troubleshoot and resolve issues related to the '''Web page is visited''' automation trigger in ActiveCampaign, ensuring a streamlined customer engagement process.
```