Show Menu
TOPICS×

9.8 Verify Data Ingestion from website into Platform

After implementing the Google Tag Manager Tag on your website, you should start to see calls being sent towards Adobe Experience Platform.
These calls are sent to the DCS Endpoint that you configured in Exercise 9.4.
To verify if calls are being sent, open your website by going to http://localhost:8888/index.html in Chrome and at the same time open the Chrome Developer Tools.
Open the Chrome Developer Tools on the Network view and then refresh your page.
By refreshing your page, you'll see all the calls being sent from the page to various servers, including the calls to the DCS Endpoint of Platform.
Go to the Console view.
In the Filter , type GA .
You should now see a log entry that says >>>>> GA - All General Pages - Sending PageView to DCS . This indicates that the call from your Google Tag Manager tag All General Pages has fired.
Go back to the Network view.
To easily find the calls to Platform, you can apply a filter by entering dcs in the Filter field.
This should give you two calls to Platform, which are the calls that sends in ExperienceEvent data on every page load, now sent by Adobe Experience Platform Launch and also, Google Tag Manager.
The first call is the call sent by Google Tag Manager. Click on it and scroll down until you see Request Payload .
Click on view source to view the full raw call to Platform. Select the full raw text and copy it.
Go to https://jsonformatter.org/json-pretty-print and paste the copied raw text in the left window.
Click on Make Pretty to see a readable version of the call to Platform. You now see the full payload as sent by Google Tag Manager to Adobe Experience Platform, and you can also see that the only identifier on this call, the Primary Identifier, is the Google GAID . This also means that with Platform, the presence of the ECID isn't a hard requirement anymore. Any identifier, including non-Adobe identifiers, can be the Primary Identifier, it's up to the customer to choose.
Next, click on any Product like the Nadia Elements Shell . Keep the Chrome Developer Console open.
Go to the Console view. In the Filter , type GA .
You should now see a log entry that says >>>>> GA - All Product Pages - Sending PageView to DCS . This indicates that the call from your Google Tag Manager Tag All Product Pages has fired.
Go back to the Network view. To easily find the calls to Platform, you can apply a filter by entering dcs in the Filter field.
This should give you two calls to Platform, which are the calls that sends in ExperienceEvent-data for a Product View, now sent by Adobe Experience Platform Launch and also, Google Tag Manager.
The first call is the call sent by Google Tag Manager. Click on it and scroll down until you see Request Payload .
Click on view source to view the full raw call to Platform. Select the full raw text and copy it.
Go to https://jsonformatter.org/json-pretty-print and paste the copied raw text in the left window.
Click on Make Pretty to see a readable version of the call to Platform. You now see the full Product Page payload as sent by Google Tag Manager to Adobe Experience Platform, and you can also see that the only identifier on this call, the Primary Identifier, is the Google GAID . This also means that with Platform, the presence of the ECID isn't a hard requirement anymore. Any identifier, including non-Adobe identifiers, can be the Primary Identifier, it's up to the customer to choose.
Next, go to to the Login/Register-page http://localhost:8888/login-register.html .
Fill out all the fields and click Create Account .
After clicking the Create Account button, you're sent to the homepage.
In the Chrome Developer Console, go to the Console view. In the Filter , type GA .
You should now see a log entry that says >>>>> GA - All General Pages - Sending PageView to DCS and also another log entry that says >>>>> GA - All Authenticated Pages - Sending PageView to DCS . This indicates that the call from your Google Tag Manager Tag All General Pages and the GTL Tag for All Authenticated Pages has fired.
Go back to the Network view. To easily find the calls to Platform, you can apply a filter by entering dcs in the Filter field.
This should give you four calls to Platform, which are two calls that send in ExperienceEvent-data for a General Page View and two calls that send in Profile-data, now sent by Adobe Experience Platform Launch and also, Google Tag Manager.
The 3rd call is the call sent by Google Tag Manager containing Profile Data. Click on it and scroll down until you see Request Payload .
Click on view source to view the full raw call to Platform. Select the full raw text and copy it.
Go to https://jsonformatter.org/json-pretty-print and paste the copied raw text in the left window, then click on Make Pretty to see the full payload in a readable format.
Again you notice that the identifiers-object contains a Google GAID . In this case, for Profile data, the Primary Identifier is emailId , with GAID being a secondary identifier. By having both of these identities on the same call, including the mobilenr , ID-syncs have now been done and have connected these 3 identities to each other in Adobe Experience Platform's Unified Identity Service.
If you see all these calls going out to the DCS Endpoint from GTM, that means that GTM is correctly configured.
Now we need to verify whether these calls are successfully received by Platform.
To log in to Platform, go to https://experience.adobe.com/platform/home .
Go to Datasets and locate your two Datasets. As a reminder, the shared datasets we're using are called:
  • Website Interaction Dataset name:
    • AEP Demo - GA Website Interactions
  • Website Registration Dataset name:
    • AEP Demo - GA Website Registrations
Datasets in the UI of Platform are usually updated every 15 minutes.
You can immediately see if the ingestion of the last batch of data for this dataset was successful:
And by opening the AEP Demo - GA Website Interactions -dataset you can see all individual ingested batches for this dataset.
By clicking on Preview , you can see a preview of the ingested data.
You can do the same thing for the AEP Demo - GA Website Registrations dataset:
Also have a look at the Preview of Profile Data to retrieve your ingested data.