Roq.ad

20/10/2023

23/08/2022

B U C K L E__U P for an introduction to our Roqad rebrand.

(cue the music...or just press play on our launch video)

Broad and relevant digital audiences are harder to reach than ever before.
and - Roqad is your solution for data that drives audience reach and attribution.

This rebrand recognizes the guts it takes to solve problems that are further off in the future.

It’s easy to focus on what’s directly in front of you.

The truth is, it’s kind of safe.

But the safe approach never took companies from good to great.

With Roqad you won’t just be prepared for the next step, you’ll be prepared for the two or three laps after that.

Roqad re-brand: a new look and feel It’s a big day for Roqad. We’ve been on a roll lately (remember that series A announcement a few weeks back – we’re still squealing). Today feels like that moment when the hero in a fast paced car chase catapults over the open chasm, smashing down in glori...

17/11/2020

Roq.ad is hiring. We're looking for a DATA SCIENTIST and some ENGINEERS (java and/or scala).

Reach out to Bartek Bogacki if you think you're good enough to build next generation enterprise SaaS toolsets.

https://roq.ad/job/software-engineer-mf

We are looking for a Software Engineer to join our team. Our ideal candidate will be creative, enthusiastic and good at getting things done.

26/10/2020

Tips for continuing to do attribution with after Apple's IDFA and Google's third-party cookies go away: here's a free survival kit resource to download for Publishers, Advertisers, and Third Party Data Providers.
👇👇👇
https://bit.ly/2HzoL61

16/10/2020

Vote for Roq.ad to speak at E-Commerce Berlin EXPO!

Roq.ad could present on how they helped RMS connect all of their users' devices including smart speakers (e.g. Amazon Alexa) to their respective owners to serve synchronized advertising across all consumer devices, optimizing their ad spend.
https://ecommerceberlin.com/vote/117594

Vote now! Carsten Frien from Roq.ad may present on February, 18 in Berlin. Free tickets available!

13/10/2020

We are looking for a couple of rocking software engineers (java/scala) and a lead data scientist to join the band. The cool thing about the gig is that you'll work with True Big Data---we're talking terabytes and clusters. You'll have fewer analytical tasks and more of the good stuff --- machine learning and prediction.

Agile/scrum/100% remote but if you want to work in Berlin, Poznan, Warsaw or Lithuania, that would be cool too.
https://roq.ad/job/roq-ad-data-science-machine-learning-roqstar

09/10/2020

Who would you like to see live on the E-commerce Berlin Expo stage? How about a vote for Carsten Frien?

Vote Carsten in 2020: https://lnkd.in/ewvFtkv

A vote for Carsten is a vote for change...
..as well as a 52% digital media cost reduction for Leroy Merlin’s offline visits with Roq.ad Cross Device Technology.

Vote now! Carsten Frien from Roq.ad may present on February, 18 in Berlin. Free tickets available!

24/09/2020

Recommendation #4 for surviving the IDFA Apocalypse.

After IDFA goes away early 2021, existing data will have a mass scale loss, so it’s important to future-proof immiediately. We talked about recommendations for Publishers and Advertisers, but what about third party data providers like Cubic, Place IQ, Blis, SITO, NinthDecimal? They have a different set of needs from Publishers and Advertisers, although similar ideas. If we can get our Publishers to stitch emails, that’s great. If not, we need to generate a per publisher ID for them.

The difference is what you’re collecting.
If they want to get anything off of the device, the SDK won’t be allowed to do it unless they get an acceptance through Apple's SKAdNetwork. (cont.)

23/09/2020

Super excited, we just hired a Software Engineer in Poznań.
We need two more! And a Data Scientist.

Join us, like the sign says, we are hiring. PM our CTO Bartek Bogacki & check out our career page for the descriptions: https://roq.ad/company

22/09/2020

APPLE-IDFA-APOCALYPSE Recommendation 3 (this one is for Publishers): Regarding the relationship between the SSP and the Publisher... We recommend that mobile publishers prepare to pass their own identifier next to the IDFA when they have it.

Option 1: If you can get access to the IDFA because a user opted-in, great, use that as the identifier of choice.

Option 2: If you can get access to email, turn that into an email token.

But there will be a lot of cases where neither of those options are available, in which case Publishers need to start generating their own identifier for that device on their app. If they don’t, then the SSP will do that for them, and it will be harder for individual ad partner DSPs to generate a back key for that. The story is “more exposure” on the advertiser side, and the story on the publisher side is “ad identifiers."

18/09/2020

On prepping for post life: if you’re an Advertiser, and you can’t collect some or all user emails, you need to prep yourself to pass more information to your or ad network partner. You will have to give them ongoing log file access to your mobile users, as well as pixel access to your web users. Pixel access will shift from their third party ID to your first party ID.

Now is a good time to start looking into it. :)