The purpose of this article is to provide a suggested approach for using EventStream once you are live that would allow you to update or amend live connectors without the risk of loss of data.
In this article:
You will need an EventStream Attribute "test_data" that will provide you a means to seperate ‘live’ events and your testing/QA events.
There are a number of ways that you would be able to pass this data point. The aim is to ensure that this test identifier is passed along with all relevant test data events.
You can setup an Event Boolean attribute "test_data" with enrichments based on existing event attribute within EventStream.
You can set the data before it gets passed to EventStream using iQ extension.
You could leverage existing data or a cookie value you’ve set via a query string.
You can set this within the code of your QA or dev site as part of the data layer.
utag_data.test_data = 'true';
When defining an File Import add a column for test_data. Test rows can have the value "true" here. You can map the test_data column to the test_data event attribute you defined above in the File Import definition.
For live File Import files if you omit the column from the file, it will still process and nothing will get flagged as test data.
If you are submitting events via the API you can simply append the ‘test_data=true’ to your call and it will process this as if coming from event source (i.e. no additional enrichments would be needed)
The Collect API also supports a POST method, with JSON as the payload. In that case, you can include a “test_data” attribute in the JSON object, with a value of true;
“test_data” : true
Once you have a data point to distinguish between live and non-live event, a mirror of your Event feeds need to be created.
For each event feed you use, you will need to create it again with the added stipulation of the test_data flag being set.
We would recommend that you create separate connectors for the test feed(s).
For successful usage once live we would recommend at least two identifiers be included within the Title of the connector:
In this instance the connector title should convey simply the Version information.
If you take this approach, you need to ensure that all connector actions are updated when you are looking to do an amend or publish a change
Assume that you have created all your event feeds and associated connectors and the system is now live. The preparation configuration should also be completed and you have mirrored each used feed with a test feed.
You only need a test feed for feeds that you have an assigned action.
If you wish to now create an amended version these are the suggested steps:
We would recommend a save as and reference the connector you’ve created
You can repeat 5-6 as many times as needed until you are happy that all changes are complete.
Once testing is complete and you are ready to push your change live you will need to walk through the following steps:
As well as the names we would highly recommend that you use the ‘Notes’ input for each connector to detail more information such as: