How do we, as a client, integrate with Roqad technology?
The second integration type (server-to-server or s2s) is just a RAW data file sharing using (s)FTP or AWS S3. For this scenario some additional criteria must be met, i.e. presence of all required attributes in the data exports. Before the project starts, we always engage the Customer Team in a use-case clarification discussion to make sure the most beneficial way of integration is chosen.
What is the difference between deterministic and probabilistic approaches? Can’t I do cross-device with my log-in data only?
Deterministic data (also called “label data”) includes information such as user name, email address, etc. tied to a specific user. It is considered one of the most accurate ways to identify a person in the online world. Typically, social media platforms, gaming sites, and large eCommerce businesses have the largest number of log-in data. However, when the person moves away from these platforms to other digital properties or does not login to a specific app or website, it is almost impossible to track the user across their multiple devices. Here, a probabilistic approach is needed in order to solve for online identity resolution.
Probabilistic data itself means observation data that does not contain a persistent identifier belonging to a given user (e.g. an e-mail address). A probabilistic identity solution collects a wide range of signals from the observation data and computes connections between the underlying device identifiers. The more matching attributes that are received and mapped for a given device and user, the higher the likelihood that these device identifiers belong to the same person.
In summary: A deterministic Cross-Device solution works well, as it holds high precision level between the device connections; however, it lacks in scale. Using a probabilistic solution in addition to the deterministic one increases scale of the model at relatively high precision rates (+90%).
What are the other use cases for which Identity Graph could be used?
Some of the common use cases for the Graph include:
- Cross-device retargeting -> reaching more devices of people from the group of your interest – perfect for branding campaigns
- Cross-device analytics -> including media mix performance measurement, attribution, funnel analysis
- BI driven insights -> creating personalized reporting, showing holistic view of the audience / users
- Performance optimization -> making informed decision about the digital budget allocation
- Sales recovery for affiliate marketing networks
How does Roqad collect consent from the user for Cross-Device (i) targeting, (ii) analytics and (iii) linking device identifiers?
Roqad filters the traffic of its data partners on user consent for Roqad. Here, Roqad uses the technical mechanisms of the IAB Europe Transparency and Consent Framework.
Roqad has vendor ID_4 on which the filter is set, thus we receive only device requests containing user consent for Roqad.
How does Roqad solve Cross-Device matching for devices that are used by multiple users?
The Cross-Device matches we produce are of high precision and generally reflect the similarity between devices and similarity between how they are used by particular people. The high precision requires that a device has to be similar to a particular user.
Therefore device with unspecific usage characteristics (because used by many people) will most probably not connect to any user. Additionally, if a device is highly similar to many potential users, which is rather uncommon, it will typically connect to the user that it’s most similar to it. Moreover, Roqad filters users that are too big in size, which is an additional reason why the device most probably will not connected to any other device.
What is the Roqad USP?
Roqad USP is privacy compliance and strongest local Cross-Device database in central Europe.
Roqad works on 100% opt-in users, and thus, is operating under the guidelines of the ePrivacy directive.
Active user consent means that Roqad will not process any data without a user agreeing to it. The user’s consent for processing can be withdrawn anytime via several opt-out mechanisms.
Which geographies are covered by the Roqad Graph?
Roqad provides identity products that are covering different regions.
Our Private Identity Graph is available globally, the Roqad Public Identity Graph is live in the European Union and North America. Roqad Link, which is our data onboarding product, is also live for EU/UK and the United States.
When will I get the Graph and Link results?
How does the algorithm work?
Is Roqad open to making a custom tailored solution?
We strongly recommend talking with our Team to discuss your use case / needs in depth. In most cases, our standard products Roqad Identity Graph and Roqad Link data onboarding are sufficient to meet the customer’s expectations.
However, we are always open to discussions concerning improvements – that’s why we invite our clients to talk about their product roadmaps and ideas every quarter.
How does intelligent tracking prevention (ITP) impact your Cross-Device solution?
The entire adtech ecosystem has been impacted by Intelligent Tracking Prevention (ITP) regulations from the various browsers. In general, large adtech businesses with high login rates are the ones that benefit from ITP regulations.
For Roqad’s Graph product, this means:
- Safari browser: Cookies are cleaned as users no longer contact the tracking domain in the last 30 days,thus, 3rd party tracking is not possible
- Chrome browser: Roqad has made all necessary changes to enable tracking of cookie IDs with Chrome 76 - deprecation of third-party cookies in Chrome expected in 2023
- Firefox browser: Enhanced Tracking Protection is installed automatically for Firefox users - list of blocked tracking domains
- Other major browsers have not yet announced any tracking prevention measures (eg Opera, Internet Explorer, etc.)
How do we eliminate erroneous data in the truth sets (deterministic data) that our clients deliver?
We do remove strange outliers to avoid skewing of the performance metrics. The cut off will be discussed with the client. For example, if we find 20 cookies connected to one hashed email address (HEM), then it’s most likely that it’s not a single user. In a 30 day window, there are usually 1 or 2 MAIDs tied to a HEM. If there are 20 or more, then it’s probably erroneous, a bot, or a shared account. We only want users that are potentially commercially viable for our clients so we remove the outliners.
Additionally, Roqad advises each client to pre-filter and cleanse the delivered data as much as possible to avoid running into skewed results.