- Analytics Components Guide
- Dimensions
- Dimensions overview
- Dimension compatibility
- All search page rank
- AM/PM
- Browser height
- Browser type
- Browser width
- Browser
- Campaigns
- Category
- Cities
- Color depth
- Connection type
- Cookie support
- Countries
- Custom link
- Customer loyalty
- Day of month
- Day of week
- Day of year
- Day
- Days before first purchase
- Days since last purchase
- Days since last visit
- Domain
- Download link
- Entry dimensions
- eVar
- eVar (Merchandising)
- Exit dimensions
- Exit link
- First touch channel
- First touch channel detail
- Hit depth
- Hit type
- Hour of day
- Hour
- Identified state
- Java enabled
- Language
- Last touch channel
- Last touch channel detail
- Marketing channel
- Marketing channel detail
- Minute
- Mobile dimensions
- Monitor resolution
- Month of year
- Month
- Operating system types
- Operating systems
- Original referring domain
- Page URL
- Page
- Pages not found
- Paid search
- Persistent cookie support
- Product
- Prop
- Quarter of year
- Quarter
- Referrer type
- Referrer
- Referring domain
- Regions
- Return frequency
- Search engine
- Search keyword
- Server
- Single page visits
- Site section
- Time prior to event
- Time spent on page
- Time spent per visit
- Tracking code
- Tracking opt-out reason
- US DMA
- US states
- Visit depth
- Visit number
- Week
- Weekday/Weekend
- Year
- Zip code
- Metrics
- Metrics overview
- Average page depth
- Average page views per visit
- Average session length
- Average time on site
- Bounce rate
- Bounces
- Cart additions
- Cart removals
- Cart views
- Carts
- Checkouts
- Content velocity
- Custom events
- Entries
- Exits
- Instances
- Mobile views
- New engagements
- Occurrences
- Orders per visit
- Orders
- Page events
- Page views
- Pages not found
- People
- Product views
- Reloads
- Revenue
- Searches
- Single access
- Single page visits
- Time spent per visit
- Time spent per visitor
- Time spent overview
- Total seconds spent
- Unique devices
- Unique visitors
- Units
- Visitors with Experience Cloud ID
- Visits
- Segmentation
- Calculated Metrics
- Calculated and Advanced Calculated (Derived) Metrics
- Frequently Asked Questions
- How-to videos
- Calculated Metrics Workflow
- Calculated metrics workflow
- Find metrics
- Build Metrics
- Metric Type and Attribution
- Build a simple “Page Views per Visits” metric
- Segmented metrics
- Stack and replace segments
- Filtered and weighted metrics
- Order Assists Metric
- Use functions
- Participation Metric
- Tag calculated metrics
- Approve calculated metrics
- Share calculated metrics
- Calculated Metric Manager
- Metrics reference
- Virtual Report Suites
- Cross-Device Analytics
- Alerts
- Classifications
- Calendar events
- Real-time reporting
- Marketing Channels
Field-based stitching
Cross-device Analytics provides two distinct methods to stitch data together. This method relies on an Analytics variable, such as a prop or eVar, to contain a person identifier. It uses that variable as a base to link devices together.
Prerequisites specific to field-based stitching
If you intend to implement Cross-Device Analytics using field-based stitching, the following are required. Work with teams within your organization and your Adobe Account Manager to ensure that you meet all of the following.
IMPORTANT
Failure to meet all prerequisites can result in the inability to enable Cross-Device Analytics or poor results when stitching data.
- All prerequisites listed on the overview page.
- Your implementation must set a prop or eVar that uniquely identifies an indivual whenever possible, such as when a user logs in or opens an email. This requirement applies to all platforms, including mobile apps if used. Communicate the desired identifying variable to your Account Manager when provisioned for Field-based stitching.
Limitations specific to field-based stitching
- Field-based stitching works best on report suites that have a high user identification rate. If your report suite has a low identification or login rate, consider using the Co-op graph.
Next steps
Once your organization meets all requirements met and understands the limitations, you can start Setting up Cross-Device Analytics.