Cross-device targeting identifies and reaches the same user across their smartphone, tablet, laptop, and connected TV to deliver consistent, sequential ad experiences.
Quick Answer
Cross-device targeting identifies and reaches the same user across their smartphone, tablet, laptop, and connected TV to deliver consistent, sequential ad experiences.
Average users own 3.6 devices, cross-device targeting prevents duplicate impressions and caps frequency at the person level
Cross-device targeting reduces effective CPM 15-20% by eliminating duplicate exposures across devices
How Cross-Device Targeting Works
Cross-device targeting solves the fragmentation problem created by the average user owning 3.6 connected devices. By linking device identifiers, cookies, mobile advertising IDs (MAIDs), hashed emails, and IP addresses, through a device graph, advertisers can recognize the same person on their work laptop, personal smartphone, and living-room smart TV. This enables sequential storytelling (show a teaser on mobile, deliver the full pitch on desktop), accurate frequency capping across devices, and multi-touch attribution that accounts for every touchpoint in the customer journey. Without cross-device resolution, a user might receive the same ad 15 times across devices while the advertiser believes they've only served 3 impressions.
Why Cross-Device Targeting Matters for B2B Marketing
In B2B marketing, cross-device targeting is critical because the average enterprise purchase decision involves 6-10 stakeholders across multiple devices and timeframes. A CMO might research a solution on their phone during a commute, evaluate vendors on a work laptop, and consume video content on a home TV. Cross-device targeting ensures your message reaches them in all these contexts with appropriate creative and messaging adapted to each environment and stage of awareness.
Cross-Device Targeting: Best Practices & Strategic Application
Best practices include using deterministic matching (logged-in identity data) as the foundation and probabilistic matching to extend reach. Cap frequency at the person level, not the device level. Segment cross-device audiences by journey stage, awareness ads on CTV and mobile, consideration content on desktop. Invest in identity resolution partners like LiveRamp, Tapad, or the identity graphs built into major DSPs. Post-iOS 14, probabilistic matching has become more important as IDFA availability has dropped.
Agency Perspective: Cross-Device Targeting in Practice
MV3 implements cross-device targeting as part of every programmatic media plan. We configure device graphs within DSPs to ensure B2B clients aren't paying for duplicate exposures. This typically reduces effective CPM by 15-20% by eliminating wasted impressions on already-exposed devices, while improving attribution accuracy by 30-40% compared to single-device tracking.
Cross-device targeting identifies and reaches the same user across their smartphone, tablet, laptop, and connected TV to deliver consistent, sequential ad experiences.
Cross-device targeting works by linking device identifiers (cookies, MAIDs, IP addresses) through a device graph, either deterministically (via logged-in user data like email) or probabilistically (via behavioral signals and statistical modeling). Major platforms like Google, Facebook, and The Trade Desk maintain proprietary device graphs. Third-party providers like LiveRamp and Tapad offer device graph services for use across DSPs.
Apple's App Tracking Transparency (ATT) framework, launched with iOS 14.5, requires explicit user permission to access the IDFA (Identifier for Advertisers). Opt-in rates average just 30-40%, significantly reducing deterministic mobile identity data. This has increased reliance on probabilistic matching, hashed email-based identity resolution, and first-party data strategies for cross-device targeting on iOS devices.
Cross-device targeting refers specifically to identifying the same user across different hardware (phone, laptop, TV). Cross-channel marketing refers to coordinating messaging across different media channels (paid search, social, email, programmatic). Cross-device targeting is a technical capability that enables better cross-channel marketing by ensuring consistent identity resolution across touchpoints.
MV3 Marketing helps B2B companies apply these strategies to drive measurable pipeline growth. Our team executes ppc management for technology, SaaS, and professional services companies.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
