Send Hashed First Party Data on Singular Events
Event attributes with hashed first-party data can be sent on Mobile, Web, PC, and Console events to improve matching accuracy with your ad network partners. Attribute names are standardized and pre-configured to work with all supported CAPI integrations. Work with your developer to add event attributes to your Singular Event implementation — details can be found in the respective SDK and S2S guides for your platform. For an overview of Singular's Conversion API integrations [read more].
Event Attributes
The following attributes should be sent as described below. These attributes are case sensitive.
| Event Attribute | Description |
|---|---|
| eventId | Event ID used for event deduplication in partner platform. Should be unique for each event. |
| ehash | SHA256 hash of email |
| phash | SHA256 hash of normalized number including a country code, e.g., “15551234567” for the United States |
| fnamehash | SHA256 hash of first name |
| lnamehash | SHA256 hash of last name |
| external_id | Singular Custom User ID - setCustomUserId method |
| phashE164 | SHA256 of normalized number including a country code and preceding ‘+’, e.g., “+4915123456789” for Germany |
| rdt_uuid | _rdt_uuid generated from Reddit's first-party pixel cookie on your domain (used in Reddit Conversion API only, when available) |
| etag | Custom tag associated with your event. For example, “back-to-school campaign” |
| page_url | Website URL where tag was fired - only used in Snapchat Conversions API (S2S) |