DTP Advertising Live: About The Data
DTP Advertising Live is quite literally meant to start a discussion around a promoted concept. They become micro-communities, and are even shareable resources like a post, article, stream, channel, library, or video.
And for what could be the first time you will see all the data the advertiser sees. If it's data in this system, and if an advertiser or administrator can see that data, so can you. Live.
Who Can Use It?
DTP publishers and DTP itself are the only entities that are allowed to create ads on the platform. We do not accept advertising from off-platform companies or people. Everyone with an account in good standing will be able to see the data presented by the system. The public will not be able to see advertisement data.
We do not accept political advertising. Politicians, political action committees, and politicially-oriented organizations are not eligible. Wokeness is not tolerated. No anti-White content or ideologies will be approved. No promotion of homosexuality, porn, or transgenderism will be permitted.
As part of the data involved with Advertising, events are logged about each advertisement, the impressions they make, and the engagements they receive. Things like time and general location are recorded and reported. Your IP address is not. Your identity is not. Your "user" identity on the system is not.
Everything you are about to read about will be presented to you exactly the same as it is presented to the advertiser. These are the events reported per advertisement per view and engagement. All of this data is anonymous.
The advertisement was selected by DTP Advertising Live for delivery to a browser. This does not guarantee the advertisement will be seen. It just means the advertisement had a chance to be seen.
Failure to be seen is a metric we use to improve the advertising system itself. We try to make sure that ads are being seen. If the metric is too low, we may add things like prompts to please turn off your ad blocker and support the shows you love.
Your ad was actually rendered into view (seen), or something significant about being seen has happened.
If a video advertisement, for example, events are received (in real-time) when playback starts and when a video plays to completion. There are other actions logged that are detailed in the Action section below, but Impression data is all about the impression the advertisement made while in the browser. This includes time information (was visible for h:mm:ss).
This information is useful to the advertiser, and helps them improve their ads. It includes exactly zero personal information. It's quite literally just numbers and timestamps. One of them is the click-through ratio. It is determined by dividing the total number of engagements by the total number of Impressions. The Click-Through Ratio (CTR) helps the advertiser determine the effectiveness of the advertisement (did they do a good job?).
The visitor did something. They sent an email, submitted a testimonial, subscribed to your channel, or even visited a link you included in your ad's content body.
Actions are recorded for video ads when the video is un-muted (made audible), muted, and paused. Those are viewer actions, not Impression actions. And, that is why they are recorded as an Action on the advertisement. These Action stats all combine to form the "Total Engagements" statistic.
When an advertisement includes a video, most actions also include a timestamp within the video. These timestamps are then used to generate what are known as heat maps to let an advertiser know you were or were not into what they had to say (dipped or skipped).
Interacting With Advertisements
Advertisements in DTP Advertising Live are meant to work like micro-communities, and implement a lot of (fun?) features that people can use to help promote, support, and build with their favorite publishers on the DTP ecosystem.
Your "downvote" on an ad is to Skip it or Mute it. Or, don't Unmute it. You can also use Contact Advertiser and give them feedback. Don't be abusive, they can just block you. But, if you're trying to help they'd love to get the feedback. Again, these are micro-communities and are meant to be conversations. And, our community is made of people who help each other. These tools are for them.
Un-muting is a "Like" in terms of data. This lets the advertiser know you were into their message and wanted to literally hear more. Letting an ad play to completion is also a "Like" in the data pile. Advertisers can't see and won't know who un-mutes or does anything else. They just get the numbers showing that their ad is working - or not working. And, you can send them email.
The "uber-like" is the Testimonial Review. If you are compelled to do so, you can write up a description of your experience and share it with the Advertiser. When doing that, you can indicate you'd be okay with it being shown to the public. If the Advertiser agrees, your testimonial becomes part of the ad.
The system does use the IP address of the requesting device (your device) to "geolocate" the request. This allows the system to provide basic anonymous geographic information about where an advertisement is being seen. It is not guaranteed to be correct. DTP does not ask members for location information, and they are not required to be accurate about their location (past, present, or future).
VPNs are not circumvented. If a request is made through a VPN and that VPN is in Guam, then the request came from Guam and that's how it will be reported. No attempt is made to correct this. If literally everyone is using a VPN, location data is worthless. And, that is hilarious, not sad. If not having accurate location data makes you sad, then DTP Advertising Live might not be the right system for you.
The goal is to provide rough/vague city, state, and country information that lets us draw cool maps with bubbles on them. The bubbles may have numbers in them. Those numbers won't be your IP address.
We are using GeoIP-Lite to perform these lookups. The output of GeoIP-Lite is what is stored (minus any IP address information, including "ranges"). The request client IP address itself is not stored. Proxy addresses are not stored. The result of the lookup is what is stored.