List of tracked events¶

Important note about event tracking¶

1. Each event’s payload contains required and optional attributes. These vary depending on the event type. If an attribute is not applicable to you (or the data is not available on certain pages), do not include those attributes.

2. You can review your website or mobile app, and implement the appropriate events wherever they are relevant. For example, a click on the Quick Add to Cart button must be tracked through a cartUpdated event, a click on the Quick View button must be tracked through a productBrowsed event, an anonymous visitor filling a form with the email address could trigger a login event. The CDP implementation team can assist you to ensure that the right events are tracked at the right places on your website or mobile app.

3. Visitors need to be identified on every event. As mentioned above, you should send a customer entity along with each event in on each object/ entity on every call when possible.

4. The attributes and values that you send to the SDK are case sensitive, and will not work if you use the wrong casing. For instance, if you identify a customer’s email, you would send us

   var currentVisitor = $A1.Customer({
   SourceCustomerNumber: "123",
   Email: “[email protected]” //”Email” with a capital “E”
   });
   

   And not

   var currentVisitor = $A1.Customer({
   SourceCustomerNumber: "123",
   email: “[email protected]” //”email” with a lower case “e”
   });
   

5. You should not initialize an object if you do not want/intend to send that object. For instance, if you are not planning to send transactions via the webtag because they do not match your Order Management System for instance (see the warnings in CDP entities about multiple source systems), do not initialize a $A1.Transaction({}) object. They add SourceTransactionNumber to event object using targets. This way we do not add anything to Transaction Entity and add information to Event and Customer Entity with SourceTransactionNumber added to Event Entity.

6. In addition to the entities you are sending to CDP, the SDK will collect additional information in each request. The list of items below will be collected :

   • UserAgent - This will be collected off of the browser (if present).
   • UserClient - This defaults to “B” (for “browser”).

List of events¶

In all cases below, it is expected that the SourceCustomerNumber or Email will be set whenever possible.

Next steps - Payload Examples¶

Now that you know what events are important for CDP to track, you can dig into the actual payloads that need to be sent to CDP to achieve this tracking. All of the events above have example payloads documented & explained in the next article : Examples of web event tracking.