Tag based campaign restrictions

With Blueshift, you can use the tag based restriction feature to restrict:

  • The audience of a campaign
  • The adapter that you can use for sending messages

Use case

Let’s say your company has 2 brands “Hooli Essentials” and “Hooli Plus”, and 2 domains corresponding to each brand - hooli-essentials.com and hooli-plus.com. Some of your customers may have signed up for hooli-essentials.com for a free (ad-driven) service. Some other customers may have signed up for hooli-plus.com for a premium (ads-free) service.

You may want to run a campaign for Hooli Plus customers. For that you can create a segment of Hooli Plus customers matching your criteria. But then at the time of launching the campaign, you accidentally select the email adapter corresponding to Hooli Essentials. Your Hooli Plus subscribers would not be pleased (to say the least) to see a message coming from hooli-essentials.comUsing tag based campaign restrictions can help you avoid such simple user errors which could hurt your brand credibility or cause huge legal expenses.

 

Note

This option is available only if the tag based campaign restrictions feature is enabled for your account. To enable the tag based campaign restrictions for your account, reach us on: support@blueshift.com.

Prerequisite

Ensure that you are familiar with creating tags and tag folders.

Set up

Let's assume that you have a campaign that targets your customers based in a specific region. And, in the campaign, you want to use a specific adapter to send emails. So you can create a tag folder similar to the one below:

sg_NA.png

Now, you can start tagging resources. Resources that you can tag include campaigns, segments, and adapters.

To start with, create a segment. Ensure that you add the restriction tags in your segment.

segment_tags.png

If you don't specify the restriction tags in the segment, you can't use it in the campaign. 

campaign_tags.png

If you add restriction tags to the segment, you can see it listed in the campaign. 

campaign_after_segment_tags.png

 

You can see that other segments are not available to use. Similarly, when you add a trigger, the option to choose an adapter prompts you to specify the appropriate restriction tags to the adapter that you want to use. 

adapter_fail.png

To add a tag to the adapter, go to the integrations page of the Blueshift web app and select the adapter from the left navigation. NA_and_SG_2.png

Now, you can choose the adapter in the campaign's trigger.

SendGrid_AMP.png

Segments and adapters can have additional restriction tags, however, the campaign can just have the restriction tags that are a common to both, the segment as well as adapter. For example, a segment can have tags t1, t2, t3. 

segment_more_tags.png

However, it's not necessary for the campaign to have all of them. The campaign can have some of those tags. Say, t1 and t2.  

campaign_after_segment_tags.png

You can still select the segment. This holds good for adapters too.

However, you cannot do the opposite. As in, it's not necessary for the campaign to have all the restriction tags that you attach to the segment/adapter. But, if there are restriction tags on the campaign, then the segment or adapter that you want to use must have them too. Otherwise, you cannot select it in the campaign. 

missing_tag_segment.png

down_arrow.png

 segment_not_available_campaign.png

Limitations

You have to perform additional steps to set up a campaign journey when this feature is enabled.
  • You can’t add a segment or create triggers if you haven’t specified any restriction tags for the campaign.
  • You cannot select a segment or a trigger in a campaign journey if you haven’t specified corresponding restriction tags on the segment or the adapter that you want to use in the trigger.

FAQ

Can I add restriction tags to the segments and adapters that some of the active campaigns already use?

You cannot add or remove restriction tags to segments or adapters that are already in use. You can add or remove tags that you use for organization, but not restriction tags.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request