If you're looking to confirm whether the CDP 365 event on your website or your app effectively captures the intended data, this document will provide valuable assistance!
Last updated
To ensure accurate event tracking and data recording for Visitors or Customers, follow these steps: visit the website, execute the desired action to trigger the intendedly-checked event, and then access CDP 365 to examine the event tracking traffic and recorded data.
To successfully test the event, it is essential to identify the specific action that triggers it.
Take that action!
Whenever a page is loaded, the 'View page' event is triggered, which implies that you will have a 'View page' event recorded for every instance of viewing any page.
The desired action is 'view' any page on the website.
Once you have performed the desired action, the event will be triggered, and you can now open the 'Inspector' or 'Inspect' tool on your desktop by clicking the right-hand mouse.
The panel will pop up on your screen.
To locate the CDP 365 events, please proceed to open the 'Network' tab and apply a filter using the keyword 'event?'.
By clicking on the event name, you can access the event details, where you will find the elements of the event documented in the API documentation.
Navigate to the Payload section, where you will discover the event log containing the event category (ec) and event action (ea) fields. These fields correspond to the Event category and Event Action documented in the API documentation and the settings within CDP 365.
This is the code sample documented in your API documentation.
You verify the event that was triggered on your 'Homepage'.
In the event details, you can find
Dims: encompass the customer data, which serves as an optional event element. This element is only available if CDP 365 can detect the identifying information of the visitor.
Portal_id: The ID assigned to your CDP 365 portal, which aids Antsomi in effectively managing our clients.
Prop_id: The ID associated with your CDP 365 source, facilitating efficient source management on your part.
UID: The Visitor ID in CDP 365 is generated by utilizing a browser cookie.
Page type and Page category are two crucial event attributes that identify the specific pages you are currently on. These attributes play a significant role in verifying the accuracy of event tracking. In the image, you will find the keyword 'Home' used as the page type and page category.
Other event attributes can be customized based on your specific data requirements.
Notes: Each event element is crucial, and if any element records incorrect data compared to what you observe on the screen, it indicates a failure in event tracking.
You verify the event that was triggered on your 'Fashion Shoes page'.
For instance, when the 'View page' event is triggered within a specific page category, it records the keyword 'category' for the page type and 'Dép thời trang' ('Fashion shoes') as the page category.
To examine the event tracking data in CDP 365, navigate to the Event Sources section.
Log into the CDP 365 system. Hover your mouse over Data on the left hand side menu → Choose Event Sources.
Choose the source that corresponds to the event occurrence, which aligns with the prop_id you observed in the event details on the website.
To verify the prop_id, navigate to the "Setting" tab.
To confirm the event details obtained from the website, navigate to the 'Events' tab and choose a specific event for verification.
Let's get back to the 'View page' event.
From this panel, you will find event logs recorded from the 'Website' source specifically for the 'View page' event within the last 6 hours.
To locate your traffic, filter the 'uid' obtained from your website.
Click on an event log to access its detailed information.
Compare the information in the event log with the details provided on your website. If they match, the event tracking works properly.
Once we have ensured correct event tracking in CDP 365, the next step is to verify whether the data is appropriately updated for the respective Visitor and Customer in CDP 365.
First, check the Visitor profile and apply a filter using the 'uid' to locate the specific profile.
Apply a filter to your User ID (uid) in order to narrow down the results.
Click on the User ID to access the Visitor profile
Review the activities recorded in the Visitor Profile. If the action and date/time of event occurrence are accurately recorded, it indicates that the data update is functioning correctly.
Next, check the Customer profile and apply a filter using the 'customer id' to locate the specific profile. The checking can only occur if the customer ID is available.
Review the activities recorded in the Customer Profile. If the action and date/time of event occurrence are accurately recorded, it indicates that the data update is functioning correctly.
For other event checks, the steps will be similar to the process of checking the 'View page' event.
This is the code sample documented in your API documentation.
To verify the 'View product' event, visit the website and view a random product on the product detail page. Then, open your Inspector tool and locate the event details within the Payload section.
The desired action is 'view a product detail page'.
Notes: For events related to products, the event details include an 'items' element to record the relevant product information such as product name, price, and SKU ...
Next, navigate to CDP 365 and select the relevant source and event.
Notes: Remember to apply a filter using your 'uid'.
Review the activities recorded in the Visitor Profile. If the action and date/time of event occurrence are accurately recorded, it indicates that the data update is functioning correctly.
Review the activities recorded in the Customer Profile. If the action and date/time of event occurrence are accurately recorded, it indicates that the data update is functioning correctly.
This is the code sample documented in your API documentation.
To verify the 'Search product' event, visit the website and search for a keyword. Then, open your Inspector tool and locate the event details within the Payload section.
The desired action is 'search for a product'.
For events related to products, the event details include an 'items' element to record the relevant product information.
According to the business requirement, the 'Search product' event is designed to track the details of multiple products. The exact number of products returned by the event is specified in the API documentation.
Next, navigate to CDP 365 and select the relevant source and event.
Notes: In the event log details, you can find the searched keyword you were looking for on the website.
Review the activities recorded in the Visitor Profile. If the action and date/time of event occurrence are accurately recorded, it indicates that the data update is functioning correctly.
Notes: You can follow the aforementioned steps to check the Customer Profile.
This is the code sample documented in your API documentation.
The desired action is 'add to cart a product'.
Next, navigate to CDP 365 and select the relevant source and event.
This is the code sample documented in your API documentation.
The desired action is 'check out the cart'.
Next, navigate to CDP 365 and select the relevant source and event.
Notes:
Please ensure that the 'Checkout cart' event accurately tracks essential revenue-related details, including quantity, price, total price, subtotal, revenue, and discount. Detailed documentation regarding this information can be found in the API documentation.
You can follow the aforementioned steps to check either the Visitor Profile or the Customer Profile.
This is the code sample documented in your API documentation.
The desired action is 'purchase your cart'.
Next, navigate to CDP 365 and select the relevant source and event.
Notes:
Please ensure that the 'Purchase' event accurately tracks essential revenue-related details, including quantity, price, total price, subtotal, revenue, and discount. Detailed documentation regarding this information can be found in the API documentation.
You can follow the aforementioned steps to check either the Visitor Profile or the Customer Profile.
This is the code sample documented in your API documentation.
The desired action is 'sign in' or 'sign up' or 'check out the cart'.
Notes: This event is triggered to align with the specific business requirements and guidelines specified in the API documentation. It can be triggered during various actions such as signing in, signing up for an account, or checking out the cart. Its purpose is to facilitate the identification of the customer ID in CDP 365 and associate it with the corresponding visitor ID.
Next, navigate to CDP 365 and select the relevant source and event.
Notes: You can follow the aforementioned steps to check either the Visitor Profile or the Customer Profile.
This is the code sample documented in your API documentation.
The desired action is 'create a new account'.
Next, navigate to CDP 365 and select the relevant source and event.
Notes: You can follow the aforementioned steps to check either the Visitor Profile or the Customer Profile.
This is the code sample documented in your API documentation.
The desired action is 'sign in to your website account'.
Next, navigate to CDP 365 and select the relevant source and event.
Notes: You can follow the aforementioned steps to check either the Visitor Profile or the Customer Profile.
The process of checking event tracking on the app is similar to that on the website.
One step that differentiates between the two platforms is how you can find your event log in CDP 365.
To ensure accurate event tracking and data recording for Visitors or Customers, follow these steps:
Step 1: visit the app
Step 2: execute the desired action to trigger the intendedly-checked event
Note: During this step, it's important to note that you won't have access to the Inspector tool to directly review the event element. Unlike the website environment where you can utilize browser tools like the Inspector to examine event details, this capability is not available when working with the app.
Step 3: access CDP 365 to examine the event tracking traffic and recorded data.
Note: In CDP 365, the event log can be filtered based on your login information (for the purchase event) or your customer ID (for other events), which may vary depending on the required login details. This typically includes either a phone number or an email address associated with your account.
To locate your customer ID, access the Customer Business Object in CDP 365 and filter by your login information.
