Use Case - Extracting Visitor IDs
- Topics:
- Admin Tools
CREATED FOR:
- Admin
Data Warehouse provides a feature that allows you to extract a list of visitor IDs. These IDs are not cookie IDs, but IDs that you capture in one of your conversion variables. Although there are other ways to get at this information, the following example is a shortcut to generating a Data Warehouse request.
For example, assume that your business sends marketing e-mails to customers and prospects. Each of these e-mail recipients has a unique ID in your e-mail system (such as EMAIL Contact ID
). You set up your e-mails so that when contacts receive an e-mail and click one of its links, the visitor arrives at your website with a campaign ID and a unique EMAIL Contact ID. For example, your e-mail link may resolve to:
https://www.test.com/?cid=springmailblast&mid=1363660158
Setting these in conversion variables (eVars) allows you to see how each e-mail performed (through the campaign ID) and how often each e-mail recipient visited the site (through the EMAIL Contact ID).
Assume you are capturing these IDs. Most marketers want to segment their website behavior and then see if they can re-market to those who meet certain criteria. For example, you may want to send a re-marketing e-mail to all e-mail recipients who came to your site from the e-mail and viewed (or completed) a website form. To do this, find a way to identify the EMAIL Contact IDs of those completing the specific form.
One way to do this is to use a Conversion Subrelation report to break down the Form ID eVar value by the EMAIL Contact ID eVar. However, a pre-built feature is available to do this using Data Warehouse. This feature allows you to tell which eVar stores your Unique User IDs (EMAIL Contact ID in this case) and allows you to easily extract those IDs using data warehouse. By using this feature, you can automatically create a data warehouse request that pulls the Unique Visitor IDs for which you are interested.
More help on this topic
Analytics
- Analytics Admin Guide
- Analytics Release Notes
- Adobe admin console
- Analytics admin tools
- Admin tools overview
- Code Manager
- Data Sources
- Exclude by IP address
- Logs
- Reporting Activity Manager
- Component migration
- Report Suite manager
- Edit settings of a report suite
- General
- General Account settings
- Internal URL Filters
- Customize Calendar
- Paid Search Detection
- Processing Rules
- Processing rules overview
- Processing Rules
- Processing rules examples
- Examples of processing rules
- Populate a campaign ID from a query string parameter
- Set the product view event from the product overview page
- Add a subcategory by concatenating the category and page name
- Determine a path by copying an eVar value to a prop
- Clean up values in a report
- Populate internal search terms using a query string parameter
- Copy a context data variable to an eVar
- Set an event using a context data variable
- Remove an event from a hit
- Processing rules tips and tricks
- Bot Rules
- Privacy Settings
- Timestamps Configuration
- Server-Side Forwarding
- Traffic
- Conversion
- Marketing Channels
- Traffic Management
- Default Metrics
- App Management
- Media Management
- Activity Map
- AEM
- Adobe Campaign
- Privacy Reporting
- Document Cloud Management
- Advertising Analytics Configuration
- Real-Time
- General
- Manage report suites
- Global report suites
- Save a report suite search
- Download report suite settings
- New report suite
- Report suite templates
- Edit settings of a report suite
- Company Settings
- Data Governance Privacy Labeling
- Server Call Usage
- User and Product Management (Legacy)
- Admin API
- Adobe Analytics 1.4 API EOL FAQ