Blueshift Best Practices
Summary / TL:DR: Best practices when using Blueshift.
Event Triggered Emails
1. If an event triggered campaign is based on a purchase event such as wmc_purchase or another custom event that is sent to Blueshift as soon as a customer purchases something, the downstream systems have to process the order and so it is recommended to not use transactional filters in the initial triggers as this could potentially filter them out of the campaign since the transaction may not yet be in Blueshift
Campaign Tags
When migrating campaigns from the legacy to the refactored instance, make sure to add in any campaign tags that were used on the legacy campaign to the new campaign. If the campaign tags are left off of the campaign, the tags will not appear in ThoughtSpot.
However, the tags in ThoughtSpot will only update if it were a recurring mailing of the same campaign name and it would update from the point in time that you fixed it. If the campaign was a one-time send, it will not be updated in reporting since that one-time mailing went out without the tag.
The campaign tags cannot be added to the campaign metadata retroactively.
Â
Still need help?
We know this can be frustrating. To get further help open a Jira ticket.