FAQs included in this article:
RTP complies with Marketo’s legal policies that can be reviewed here: https://www.marketo.com/company/legal/.
This will be updated appropriately by our Legal department based on any upcoming laws.
RTP only loads the Wistia or YouTube API when the RTP script discovers a Wistia or YouTube video embedded on the page.
How does RTP collect data on visitors?
Please see RTP - How does RTP collect data on visitors.
No, a reverse IP lookup cannot return an email address.
How does the RTP javascript work?
Please see: RTP - How does the RTP javascript work.
How are JavaScript cross-site scripting attacks mitigated by RTP?
We define a session as 30 minutes from the visitor's last click.
We do not recommend hosting the JavaScript on another server for performance reasons. It is possible, but it is not recommended.
Unlike Munchkin script, the RTP tag must have a very short loading time. If not the user experience might be affected and campaigns may have some latency.
This is also the reason why we recommend inserting the tag higher in the code, right after the <head> tag.
Yes. The RTP tag supports both http:// and https:// pages.
Please see:RTP - Can RTP campaigns be blocked by Ad or Javascript blockers?
Yes. We cover between 80-90% of known-bot user-agents and continually update the blacklist.
The RTP tag uses jQuery to assure that some functionalities will work properly on any page. However, if the jQuery causes issues with other parts of your website, we can configure the tag to disable it altogether. This can be done by the Marketo Support team because this advanced configuration is not accessible directly to customers.
Please see RTP - What are the differences between the RTP tag versions.
The trvw.uid cookie contains a VisitorID which is a GUID (Global Unique Identifier) only used by RTP to identify the web visitor for returning visits and historical behavior.
What is the RTP limitation of the number of daily visitors with Munchkin2?
RTP is not related to Munchkin. The move to Munchkin2 has no affect on the functionality of RTP.
From the visitor’s visit on site in the session, we see information such as IP, page URL, search term and referral sites.
From the IP address, we use Reverse IP lookup to match the organization name.
From the Organization name, we match it with RTP’s propiertary firmographic data including:
Install the RTP tag on ALL web assets. Including all domains, subdomains, landing pages, blogs etc. even if you do not intend to display campaigns on those assets.
The reason for this is that we want to capture the entire customer journey.
RTP tag is not sending clicks from IP URLs
This is expected behavior. The RTP JavaScript does not send clicks from IP URLs, i.e: http://63.251.134.57/
The tag is turned off. You can check this setting in Account Settings.
You can remove companies from appearing in your RTP reports, and from seeing campaigns - this is done through a support ticket request. Send them the company names or IP addresses you want to block from RTP campaigns and appearing the RTP reports.