Real-time Segment FAQ

What are Real-time segments?

Real-time segments allow you to immediately add users to a segment once segment rules are met and then target those users on the next page view. For example, you can deliver an ad on the next page view after users perform a search. 

Real-time segments are calculated at the browser level so only on-site targeting is supported. Historical activity data is not used in Real-time segments.

How do Real-time segments work?

Real-time segments allow a browser user to qualify for the segment rules immediately rather than on the next page view as is the case for standard segments. The segment ID will then be returned to the browser's local storage for immediate use.  

Users will remain in the Real-time segment for 72 hours without having to repeat the action that qualified them for the segment. A user must have a KUID already assigned in order for the user to qualify for a segment.

How do users qualify for a Real-time segment?

Example:

  • Day 1: Real-time segment sees 10 new users. Population = 10  
  • Day 2: Real-time segment sees 5 new users. Population = 15
  • Day 3: Real-time segment sees 5 new users. Population =10 (only users that qualified in the past 72 hours are now in the Real-time segment)

How often are Real-time segment populations refreshed?

Real-time segment populations are computed daily from the data that Salesforce DMP receives from pixel.gif. 

The Control Tag identifies users who fall into a Real-time segment. That information is then pushed to pixel.gif and the population will update in the UI the following day. Therefore, the UI will always show yesterday's population.

What are the targeting requirements for Real-time segments?

  • The segment automatically enabled for Onsite activation
  • The Salesforce DMP O&O snippet must be implemented on the page with key value set up. This is the piece of code that drops the segment and User ID values in local storage. Please reference the Implementation User Guide for more information.

 Note: Real-time segments are only available for onsite (O&O) targeting and cannot be targeted via other activation partners such as DSPs and SSPs partners at this time due to the reliance of Real-time segments on local storage.

Are there any rule limitations associated with Real-time segments?

For a user to qualify for a Real-time segment, all the rules for the segment must be true in a single session. Real-time segments are computed as a whole segment and not at the rule level, so you will not see populations for the individual segment rules. To see populations for the underlying rules of a Real-time segment, create a Standard segment with the same rules as your Real-time segment.

 Segment rules that can be used within a Real-time segment:

  • Page attributes (without frequency or recency)
  • User attributes
  • AND / OR operators
  • Standard segments (users must qualify for the standard segment first)
  • Users of the Safari browser which blocks 3rd party cookies

Segment rules that CANNOT be used:

  • 3rd party rules
  • Imported data
  • Technographic and geographic rules (recommended to target in ad server)
  • AND NOT operator

Can Real-time segments be pushed to mobile apps?

No, Real-time segments cannot be returned to mobile apps.

Can standard segments be used in Real-time segments?

Technically, this can be done, however the use case for this is rare.

The primary purpose of a Real-time segment is to target immediately. For instance, if a user visits a checkout page and then abandons the shopping cart, you can serve an ad on the next page view to try to get the user to return and complete the purchase. Collecting users 30 days in advance with a standard segment and then applying those users to a Real-time segment disregards this “immediate targeting” use case.

Can Real-time segments be pushed outside of onsite partners?

Currently, Real-time segments cannot be pushed to any channel other than onsite due to reliance on local storage.

How do I exclude users from a Real-time segment?

The best practice is to suppress the segment in the ad server.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk