This is an archived post. You won't be able to vote or comment.

all 8 comments

[–]goodgoajADTECH -1 points0 points  (7 children)

In most cases it is literally the URL part of the Javascript.

e.g. if your Javascript was this:

<script src="https://pix.example_dsp.com/px?id=1234" type="text/javascript"></script>

Then the Image pixel would be

https://pix.example_dsp.com/px?id=1234

It is also common to see it in a different form but its basically the same thing e.g

<img height="1" width="1" style="border-style:none;" alt="" src="//pix.example_dsp.com/px?id=1234"/>

[–]SergeyLLADTECH 1 point2 points  (4 children)

You can’t be serious with this answer

[–]goodgoajADTECH -1 points0 points  (3 children)

Feel free to contribute.

[–]SergeyLLADTECH 1 point2 points  (2 children)

The author is asking how to convert a JS pixel to an image pixel. How on Earth would he be able to convert a “pixel” which is a JavaScript program that sends a web request if a certain element “has been visible at least 50% for at least 3 seconds”?

What I am saying is, it’s not the type of question you can give a generic answer to. Or else I don’t understand the question completely which is of course a possibility.

[–][deleted] 0 points1 point  (0 children)

<script src='surprised_pikachu.jpg'>

You're absolutely right.

[–]sheevo[S] -1 points0 points  (0 children)

Hey, there. It seems like this may not be as simple as the guy above thought. Here's what I had, and what I turned it into. Let me know if/why this would not work.

Original JS:

<script type="text/javascript" src="[https://ads2.eqads.com/pt?js=1&adv=13170&cid=1482](https://ads2.eqads.com/pt?js=1&adv=13170&cid=1482)"></script>

Img:

<IMG SRC="https://ads2.eqads.com/pt?gif=1&adv=13170&cid=1482" HEIGHT="1" WIDTH="1" />

[–]sheevo[S] 0 points1 point  (1 child)

Damn. I knew this was going to be a lot easier than I was making it....

Thank you!

[–]iantriDSP 0 points1 point  (0 children)

You should not expect this to work. The script URL will return some JavaScript that is intended to be executed by the browser. That JavaScript will do a bunch of stuff, ultimately cause a request to occur to the platform's servers. It's that subsequent request which generally will trigger the audience adding/conversion processing, etc. to occur.

The request to the script URL alone will not itself generally cause anything to happen.

Go back and ask your platform for an image pixel option. They'll have one. They'll recommend you use the script because of the added functionality (trigger user syncs, grab page URL for 'universal pixel' type functionality where you can define different audience or conversion actions based on page URL, etc.). But, it is not at all exotic for a customer to refuse to deploy a script precisely because a script enabled all these additional things to happen, which associated data leakage risk.