In this step you will use Trace to validate that all of the previous configuration is working as expected. You will get a trace ID, add it to your application (or use the Tealium Tool), perform a simple test, then inspect the logs in the Trace interface.

Before you begin, if you will be testing a web page you will need the Tealium Tools browser extension. Select the install link for your browser:

Start a Trace

Follow these steps to perform a test with Trace:

  1. In the sidebar select Trace.
  2. Under New Trace, click Start.
  3. Copy the trace ID provided and click Continue.
  4. Activate the trace ID using one of the following methods:

    Tealium Tools

    Open a new browser window to your test page. Click the Tealium Tools browser extension and click AudienceStream Trace. Enter the trace ID from step 2 and click Start Trace.
    es-getting-started-trace-tealium-tool.jpg

    Data Layer Attribute

    Add tealium_trace_id to the data layer of your code installation and set it to the value of the trace ID.

    In the HTTP API, this means adding a query string parameter:
    &tealium_trace_id=012345

    In a Swift app, for example, it will look like this:
    tealium?.volatileData()?.add(data: ["tealium_trace_id": "012345"])

  5. Proceed with your test case work flow.
    This may mean refreshing the page, navigating through some pages, making a purchase, or viewing some screens in a native app.
  6. Return to the Trace interface to inspect the log details.

Trace Log

The Trace log will update automatically as EventStream processes the traced event. It will display the event data details, the matched spec, any matched feeds, and any triggered connector actions. If there were any errors, those will be provided as well with additional details of the issue.

The Trace image belows reflects the validation of the previously configured components using the "Search with No Results" example.

getting-started-eventstream-trace.png

In this case:

  • ✓ - the event spec for "search" was validated
  • ✓ - the event feed was matched
  • ✓ - the Google Sheets connector was triggered.

Beast-Thumbsup-Whistle-small.png

Here are some things to check if you didn't see the expected trace log:

  • Did you use the correct trace ID in your test?
  • Did you save and publish your account after adding the event spec, event feed, and connector action?
  • Did you set tealium_event correctly?
  • Does the value of tealium_event match the name of the spec?
  • Does your test event match the conditions of the event feed?

Great job! You've made it to the end of this simple getting started guide. The next step will quickly cover the save and publish process followed by some helpful links for additional reading.