All Device Geo-Fencing/Geo-Retargeting cannot have Audience DNA pulled on it, add lookalikes to it, have scrolling banner ads, or have dynamically inserted information into the ads. You also can't do All Device Geo-Fencing on its own and will want to [...]
What if a client wants to geo-fence an event and then save that info and geo-retarget those people later, can we do that? Yes. However, we have to serve ads during the geo-fenced period as well. The platform will not [...]
The answer to that is yes, we do. We call it Geo-Retargeting, and it's part of our Mobile Conquesting tactics that are available. It’s capturing mobile device IDs of users who have entered into a specific location (a geo-fence) and [...]
When we do Retargeting (whether Retargeting from a client’s website or Station Website Retargeting) we try and retarget from the same exchange(s) so we can balance where conversions are coming from with served impressions- once you start splitting up exchanges [...]
Yes, you should. Because while it's true you may end up targeting some people who purchased from the competitor (there will be some waste with EVERY type of advertising) you'll also target the people who were there and decided not [...]
Geo Conquesting is when we target people at competitor locations and try to serve them the client's ads Geo Retargeting is when we target people who HAVE BEEN to a location you specify (i.e. a competitor's location, an event, etc.) [...]
With Mobile Conquesting we can add in "geo-retargeting." There are two ways we can do geo-retargeting: Retarget people who have visited any location you provide us (allow two weeks for geo-retargeting to begin serving ads). These people do not have [...]
Our best practice is to collect data for 2 weeks and then start delivering to people being geo-retargeted from a location. If this is for an event, because there is typically so much data during the first couple days, we [...]
