![]() Therefore, it’s not possible to reliably alert you when a pixel is blocked, unless you have Chrome Dev Tools open and you’re monitoring the Console, as shown above. Pixel tester chrome code#Our Tracker Blocker extension is built on the latest Chrome extension specification, called Manifest V3, and this latest specification does not, by default, allow our code to fire an “event” whenever a pixel is blocked. Notifying you, the user, when a tracking pixel is blocked, is difficult, due to recent updates to Chrome. Are you notified when a pixel is blocked? Unfortunately that’s not something we can control.Īdditionally, if you’re having opens logged to the Label GMass Reports–>Opens, you will notice that a notification won’t appear here with Tracker Blocker running. We’re not sure why this is, but we suspect that Gmail is specifically trying three times to load an image when it detects a problem. You may find that when you open an email that has the pixel, that three network requests are actually blocked, and as a result, three browser notifications popup on your computer. net::ERR_BLOCKED_BY_CLIENT With Chrome Developer Tools open to the Console, you can see the entries whenever a pixel is blocked. Once you do, you’ll see a line appear in the console that looks like: GET. NOw open up an email sent by GMass that you know has an open tracking pixel. First open up Chrome’s Developer Tools by right-clicking anywhere in Gmail and choosing “Inspect”. You can test the blocking functionality and prove its working with a bit of technical wizardry. The “Block open-tracking pixels” box must be checked though to enable the pixel blocking functionality. In that case, you may want to leave the box unchecked. Perhaps you’re a new GMass user, and you want to test the open tracking functionality to see how the reports look. If the “Block” box is unchecked, then opens will register. The settings panel for Tracker Blocker is just two simple checkboxes. Obviously if you have the “Notify” box checked but the “Block” checkbox unchecked, you won’t be notified of anything. There are two checkboxes to toggle, one to block pixels and one to notify you when a pixel is blocked. If you don’t see the black GMass icon, then click the “puzzle piece” icon, find the Tracker Blocker extension in the list and “pin” it. This prevents false opens from registering if you open an email you’ve sent with GMass.Ĭlick the black GMass icon in the upper-right of your browser to open the settings panel. This extension is a simple extension that blocks network requests to our open tracking server. The Tracker Blocker extension prevents these “false” opens by preventing the browser from registering an open on your own emails. You set your campaign to create DRAFTS, and then open a DRAFT for editing.Someone replying to your email, and then opening the reply.The email bouncing, and then you opening the bounce notification.Other scenarios may also lead you to opening the email and triggering an “open”, such as: It’s impossible, however, to distinguish your contact opening the email in their Inbox versus you opening the email from your Sent folder. GMass, or any other Gmail-based campaign sending tool, sends emails directly from your Gmail account, and as a result, they are logged to your Sent folder. The Tracker Blocker extension was created to solve a longstanding problem that GMass users have - triggering “false” opens when they open an email from their Sent folder. Install Tracker Blocker from the Chrome Web Store. Pixel tester chrome install#If you’re using GMass to send campaigns, you should also install Tracker Blocker so that your open-tracking reports are as accurate as possible. Today we’re launching a new Chrome extension, called Tracker Blocker, that is a companion extension for GMass. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |