Retro fixing marketing channel processing rules issues

[MattBlake]

Hi, we've had a glitch with our Marketing Channel processing rules for a couple of days which means that traffic has been attributed to the wrong Marketing Channels.

Essentially tracking codes beginning with 'PPC' and 'display' have been wrongly assigned to the 'Email' bucket (rather than 'Paid Search' and 'Display' respectively), just for a period of two days. (the tracking codes are all working fine in themselves, though)

Does anyone know of any possible way to fix this misattributed data so that it's retro-fitted into the right Marketing Channels?

Thanks!

[Hemang35 · Accepted solution]

Sure, there are a few ways to fix misattributed data in your marketing channels.

Method 1: Use a data migration tool

There are a number of data migration tools available that can help you to move data from one system to another. These tools can be used to identify and correct misattributed data.

Method 2: Use a manual process

If you don't want to use a data migration tool, you can also manually correct misattributed data. This can be a time-consuming process, but it is possible.

To manually correct misattributed data, you will need to:

1. Identify the misattributed data.
2. Correct the data in the original source.
3. Update the data in your marketing channels.

Method 3: Use a combination of methods

You can also use a combination of methods to fix misattributed data. For example, you could use a data migration tool to identify the misattributed data, and then manually correct the data in the original source.

The best method for fixing misattributed data will depend on the size of your dataset and the amount of time you have available.

Once you have fixed the misattributed data, you will need to monitor your marketing channels to ensure that the data is accurate. You can do this by comparing the data from your marketing channels to the data from your website analytics.

If you find that the data is still inaccurate, you may need to repeat the process of fixing the misattributed data.

Here are some additional tips for fixing misattributed data:

• Make sure that you have a clear understanding of how your marketing channels work. This will help you to identify the source of the misattributed data.
• Use a data migration tool to identify the misattributed data. This will save you time and effort.
• Manually correct the data in the original source. This is important to ensure that the data is accurate.
• Monitor your marketing channels to ensure that the data is accurate. This will help you to identify any new problems with the data.

By following these tips, you can fix misattributed data and ensure that your marketing channels are accurate.

[Hemang35]

No, you do not need to create a different rule in order to send the variable in the next page. You can use the same rule to send the variable in the next page and empty the DE.

To do this, you will need to add a condition to the rule that checks if the current page is product B. If the current page is product B, then the rule will send the value of the DE in eVarX.

You will also need to add an action to the rule that empties the DE. This will ensure that the value of the DE is not carried over to the next page.

Here is an example of the rule that you can use:

Trigger: Pageview
Conditions:
* Page URL matches /product-a/
* Product ID is present in the URL
Actions:
* Set DE to Product ID
* Send DE in eVarX
* Empty DE

This rule will set the DE to the product ID of the product that the user is viewing on product A. It will then send the value of the DE in eVarX when the user lands on product B. Finally, it will empty the DE so that the value is not carried over to the next page.

You can also use this same approach to send the value of the DE in eVarX when the user lands on product C. Simply add a condition to the rule that checks if the current page is product C. If the current page is product C, then the rule will send the value of the DE in eVarX.

By following these steps, you can capture the product ID of the original page the product was viewed and send it in eVarX when the user lands on the next page.