Understanding the Requirements

In order to unify website tracking with existing profiles, a submission of an MCA landing page or form handler is required. This step is crucial for the unification process to happen. Additionally, it’s essential to check if any unification is happening at all by looking at the ‘Identity match’ object.

When building segments based on website engagement, it’s not uncommon to encounter issues, such as getting population for each criteria but 0 when saving it. This can be due to various reasons, including bugs on the back of tracking and unification.

Troubleshooting Common Issues

To troubleshoot these issues, it’s essential to check the ‘Identity match’ object to see if any unification is happening. If not, it may be necessary to review the setup of the MCA landing page or form handler to ensure that it is submitting data correctly.

The root cause of the issue is often related to the lack of submission of an MCA landing page or form handler, which is necessary for the unification of website tracking with existing profiles.

Step-by-Step Solution

To enable segmentation by website engagement, follow these steps:

Segmentation Code

1. Ensure that the website engagement data is tied to the Individual
2. Verify that both DMOs are related
3. Check the 'Identity match' object for unification
4. Review the setup of the MCA landing page or form handler
5. Test the segmentation to ensure it is working correctly

Heads up: Be aware of potential bugs on the back of tracking and unification, and troubleshoot accordingly.

Checklist for Enabling Segmentation by Website Engagement

Pre-Flight Checklist

• Ensure that the website engagement data is tied to the Individual
• Verify that both DMOs are related
• Check the ‘Identity match’ object for unification
• Review the setup of the MCA landing page or form handler
• Test the segmentation to ensure it is working correctly
• Monitor for potential bugs on the back of tracking and unification
• Regularly review and update the segmentation to ensure it remains accurate

Frequently Asked Questions

What is the ‘Identity match’ object?

The ‘Identity match’ object is used to check if any unification is happening between website tracking and existing profiles.

Why is it necessary to submit an MCA landing page or form handler?

Submitting an MCA landing page or form handler is necessary for the unification of website tracking with existing profiles to happen.

What are common issues that can occur when segmenting by website engagement?

Common issues include getting population for each criteria but 0 when saving it, and bugs on the back of tracking and unification.

How can I troubleshoot issues with segmentation by website engagement?

To troubleshoot issues, check the ‘Identity match’ object, review the setup of the MCA landing page or form handler, and test the segmentation to ensure it is working correctly.

What are the benefits of segmenting by website engagement?

Segmenting by website engagement allows for more targeted and personalized marketing campaigns, leading to increased engagement and conversion rates.