Help Center

How do we integrate with Roq.ad Technology?

We support two ways of integration: by tracking codes and server-to-server. 
The former could be done with JavaScript codes which requires either cosmetic changes (campaign or use-case specific) or for NO changes at all.
 We can also provide an IMG tracking code but in this case it needs to be customized.

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 Customer Team in the use-case clarification discussion to make sure the most beneficial way of integration is chosen.

What are the other use cases for which Graph could be used?

Among use cases are:

– 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;
– and some others.

How does Roq.ad collect consent from the user for Cross-Device (i) targeting, (ii) analytics and (iii) linking device identifiers?

Roq.ad filters the traffic of its data partners on user consent for Roq.ad. Here, Roq.ad uses the technical mechanisms of the iab Europe Transparency and Consent Framework. Roq.ad has vendor ID_4 on which the filter is set, thus we receive only device requests containing user consent for Roq.ad.

How does Roq.ad 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, Roq.ad 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 Roq.ad USP?

Roq.ad USP is privacy compliance and strongest local Cross-Device database in central Europe. Roq.ad works on 100% opt-in users, and thus, is operating under the guidelines of the eprivacy directive. Active user consent means that Roq.ad will not process any data without user agreeing to it. The user’s consent for processing can be withdrawn anytime via several opt-out mechanisms.

What geo’s is Roq.ad active in?

Roq.ad is providing several products that are covering different regions.
Private Identity Graph is available globally, when Roq.ad Public Graph is focusing on DACH region and Poland. Also, ROPO360 (Research Online, Purchase Offline) is currently live in Germany and Poland. To learn more about each product, check our Solutions

I am interested in learning more about Roq.ad, who do I contact for questions?

Please send a mail to contact@roq.ad, or fill in our contact form below. We will set up a clarification call or personal meeting to answer all questions.

When will I get the results?

The Graph computation frequency varies from Customer to Customer – from once per week up to once per month. It’s strongly dependent on the use-case and specific needs. 
First results will be delivered after ~1 month of data collection (when Roq.ad tracking scripts are used). In case of server-to-server integration, around 1-2 weeks are needed after the data is shared.

How does the algorithm work?

It’s our secret sauce :)‚ However, to understand the process a bit better we strongly suggest reading our 
White papers. Definitely it’s worth spending 30 minutes to understand the idea of cross-device matching.

Is Roq.ad open for making a tailored solution?

We strongly recommend to talk with our Team and discuss your use case / needs in depth. In most cases our standard products: Public and Private Identity Graph and ROPO360 are sufficient to meet the Customer 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 ITP impact your Cross-Device solution?

First of all, the entire industry is impacted by ITP regulations from
the browsers. In general, large Adtech businesses with high login rates are the ones that benefit from ITP regulations.

For Roq.ad’s Public Graph product this means:

- Status Safari: Cookies are cleaned as users no longer contact the
tracking domain in the last 30 days. Thus, a 3rd party tracking is not
possible.

– Status Chrome: Roq.ad has made all necessary changes to enable
tracking of cookie IDs with Chrome 76.

- Status Firefox: Users reinstalling Firefox have enabled Enhanced
Tracking Protection automatically. List of blocked tracking domains: 
here.
– 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 big users to avoid skewing of the performance metrics. The cut off will be discussed with the client. Additionally, Roq.ad advises each client to pre-filter and cleanse the delivered data as much as possible to avoid running into skewed results.

What is the difference between deterministic and probabilistic approach? 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 as 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 probabilistic solution in addition to the deterministic one increases scale of the model at relatively high precision rates (+90%).

Get in touch!



Interested in learning how Cross-Device can help your business to grow?

Send us a message and we’ll be happy to tell you more!

Request Test