Custom Audiences User Data

This document outlines the format for Custom Audience user data.

Data normalization

Device IDs:

  • IDFA - lower-cased with dashes; ex: 4b61639e-47cc-4056-a16a-c8217e029462
  • AdID - original format on device is required, not capitalized with dashes; ex: 2f5f5391-3e45-4d02-b645-4575a08f86e
  • Android id - original format on device is required, not capitalized without dashes or spaces; ex: af3802a465767e36

Email Addresses:

  • lowercase, remove leading and trailing spaces; ex:

Twitter Usernames:

  • no @, lowercased and leading and trailing spaces trimmed; ex: jack

Twitter User IDs:

  • Standard integer; ex: 143567

Data hashing

The data for each line must be hashed using SHA256, without a salt.  Additionally, the final output hash must be in lower case. E.g., 49e0be2aeccfb51a8dee4c945c8a70a9ac500cf6f5cb08112575f74db9b1470d and not 49E0BE2AECCFB51A8DEE4C945C8A70A9AC500CF6F5CB08112575F74DB9B1470D

      # hasing user @AdsAPI using python
import hashlib


Additional code samples for hashing can be found at

Was this document helpful?
Thank you

Thank you for the feedback. We’re really glad we could help!

Thank you for the feedback. How could we improve this document?
Thank you for the feedback. Your comments will help us improve our documents in the future.