Jump to Content
factualKnowledge Base
Knowledge BaseAPI Reference
Knowledge BaseLog Infactual
Log In

Marketing Solutions

  • Overview
  • Audience
    • Receiving Audience Segment Data
    • Audience Designer Custom File Upload Guidelines
  • Proximity
    • Proximity Set Upload Guidelines
  • Measurement
    • Sending Custom Places to Factual
    • Measurement Data (MD)
    • MD: Integrating Factual Measurement Data via Amazon S3
    • MD: Receiving Measurement Data TSV Files
    • Measurement Intelligence (MI)
    • MI: Using the Measurement Pixel
    • MI: Submitting Ad Exposure Data Directly to Factual
    • MI: Submitting Digital Ad Exposure Data to Factual via LiveRamp
    • MI: Submitting TV Ad Exposure Data to Factual via LiveRamp
    • MI: Submitting OOH (Out of Home) Exposure File to Factual
    • MI: Sending OOH (Out of Home) Ad Locations to Factual
  • Marketing Solutions APIs
    • Authentication
    • Tokens
    • Management
    • Grant
  • Submitting Data for Audience
    • Submitting Data via S3
    • Submitting Audience Data – Accepted Formats
    • Submitting Data to Observation Graph — Accepted Data Format

Places

  • Overview
  • Getting Started
  • Supported Countries
  • Core Attributes
    • Categories
    • Chains
    • Existence
  • Extended Attributes
  • Trusted Data Contributor Program
  • FAQ

Setting an Ad-id

If you would like the mobile user's advertising identifier (idfa) to be present in remote analytics, you may pass in the user's advertising identifier after enabling remote analytics. For example:

- (void)engineDidStartWithInstance:(FactualEngine *)engine {
  NSLog(@"Engine started.");
  
  [engine enableRemoteAnalytics];
  [engine setAdId:@"user-ad-id"];
  ...

Updated about 3 years ago