The Predict Data Sources page is a status monitoring dashboard that allows you to check if your integration has any issues to address. For example, you can immediately see if any of your web shop data collection scripts are not performing properly, or if your product database is missing any items. If problems are detected it offers you help by providing detailed suggestions on how to fix them.
In short, it is your starting point for troubleshooting any integration issues. We suggest that you check back on your integration’s health by opening the Predict Data Sources page every once in a while, and especially after updating the code on your web site or whenever you are experiencing anomalies.
Please note that when a contact is deleted, all of the data relating to that contact is also deleted. You may experience sudden changes in the Site Traffic reports after deleting contacts, but it will not affect your reports retrospectively.
For more information on the effects of contact deletion, see What happens to deleted contacts in Emarsys?
Not yet started your data onboarding? Click here to see how the Predict Data Sources page will walk you through the process.
As a quick reminder, here is the onboarding video about the Predict Data Sources page:
What can you find on the page?
The Predict Data Sources page contains a series of boxes:
Each individual data source has a dedicated box. These boxes display health status information and some basic metrics (such as when the last update occurred, the number of products, tracked revenue, etc.) about the upload or feed in question. Next to their title, a prominent indicator shows the status of the given data source as well as the number of issues, if any, picked up by the validation tools.
The color of the box frame also reflects the status of the data source. The states you may see here are:
|Title font and frame color
||Title bar indicator
So by having a quick look at this page you can immediately see if your integration works fine or has issues to address.
On the right, you can find some boxes that show if your data sources are consistent with each other. For example, if the Emarsys data collection scripts pass Product IDs which are not found in your product data, you will see warnings here.
The boxes you can see here include:
Order consistency issues occur when the Product IDs uploaded in the Sales Data file are not consistent with those found in your Emarsys product database.
Only those boxes are displayed here for which the validations can be performed. Validations will not run if one or more of the required data sources are not set up, or are outdated. For example, if you have not uploaded sales data, the Order Matching box will not be visible here.
What if there are errors?
If issues are detected in any of your data sources or during the consistency checks, the relevant boxes will display warning or error messages, depending on the severity of the problem. Just click them to expand a detailed description of the issue as well as suggestions on how to fix them.
If you see warnings or errors in any of the consistency check boxes, you can hover the mouse cursor over the given box to highlight the data sources that affect the given consistency. These are the data sources you need to look into to resolve the consistency issue.
Using the links in the top right-hand corner of the data source boxes, you can also click through to the relevant pages where, depending on the source in question, you can update your data load settings, make manual uploads, view reporting or start debugging issues.
What else can I do here?
There are a few other things you can do on this page:
Check the tracking code associated with your account
If you want to check or reuse your Emarsys data collection script code, you can always find it in the Account Details box on the bottom right-hand side. To display the code snippet, click Tracking code next to your Merchant ID.
Change your base currency
If you want to change the base currency for your account, you can do so in the Account Details box on the bottom right-hand side. Just click Change next to your current base currency.
Monitor live website events
In the Web Behavior box on the left, you can also follow your visitors’ activity on a live ticker, which displays view, category, search and purchase events in real time.
What else should I know?
Validations do not necessarily show real-time status information. Depending on the data sources used and the volume of traffic to your website, the time it takes for the validation messages to refresh may range from a few seconds to 3 days. As a result, when you fix an issue the validation warning messages may not disappear immediately, or, conversely, when something breaks in your integration warnings may be displayed with some delay.
Why is not the Contact Import box active?
This feature is still in development and will be activated in a future release.
I have run into an issue but the Predict Data Sources page does not show any errors?
Depending on the data sources used and your website traffic, the time it takes for the validation messages to refresh may range from a few seconds to a few days. See above.
I have fixed an issue but the Predict Data Sources page still shows the same error message?
My data sources are marked OK, but the page tells me there are some consistency issues. How is that possible?
Consistency issues may occur even when all data sources are configured properly and are marked “OK”. For example, if the data collection scripts pick up incorrect Product IDs on your website, these will not match those found in your Emarsys product database.
I cannot access the Predict Data Sources page. How can I enable it?
Ask your Account Owner to enable it for you by setting the switch for data onboarding in Management > User Management.
Why did I receive the "X pages called the go command multiple times" error message?
It could happen for various reasons:
- If you are using Ajax for your cart on your web shop, then you can ignore the "X pages called the go command multiple times error" message.
- If you are using a single-page application, then you can ignore this error message.
- Otherwise, it might indicate an implementation error which means that a site might call the
gocommand multiple times or at specified time intervals. This is not optimal as the
gocommand should be called only once per page load. In this case, please contact your Implementation Consultant.