Meta Pixel and Google Analytics on your pages

What it does

Connect your Meta Pixel, Google Analytics, or both, and your pages on postfjord.page can tell them about one thing: a new signup through a form on a page. Meta gets it as a Lead. Google Analytics gets it as a generate_lead event.

Your ads and campaigns can then show how many signups they bring in.

Only a person who ticks the box on your form is sent. Visits to your pages and taps on links are never sent to Meta or Google. Numbers keeps counting them for you alone, as daily totals.

Postfjord sends the signup from its own servers. Your pages still set no cookies and run no scripts, and neither Meta's pixel code nor Google's tag ever loads on them.

The box on your forms

While the Meta Pixel or Google Analytics is on, every signup form on your pages shows one more box. It is not ticked. It names what you have on:

• With the Meta Pixel: Share my signup with Meta so Sunrise Yoga can measure its ads.
• With Google Analytics: Share my signup with Google so Sunrise Yoga can measure its ads.
• With both: Share my signup with Meta and Google so Sunrise Yoga can measure its ads.

Your workspace name stands where Sunrise Yoga is, and a Privacy policy link opens your privacy policy. The box shows in the page's language, for every visitor, wherever they are.

A person can sign up without ticking it. The form works as before, and nothing goes to Meta or Google.

A signup goes only where the box said when the person ticked it. If you connect Google Analytics later, a page that still shows the older box sends only to Meta until it shows the new words.

Meta Pixel

Before you connect the pixel

You need three things:

1. Your Pixel ID. Open Meta Events Manager. Under Data sources, pick your pixel. The ID is the number under its name.
2. An access token. In Events Manager, open your pixel, then Settings. Under Conversions API, press Generate access token, and copy it.
3. The address of your privacy policy. It must start with https://. The box on your forms links to it.

Connect your pixel

1. Go to Pages. The Meta Pixel card is near the bottom.
2. Paste your Pixel ID and your access token.
3. Paste the address of your privacy policy.
4. Press Save and start.

Only the owner of the workspace can do this, and Postfjord asks you to sign in again first. The token is kept encrypted. The app shows only its last four characters. Your live pages show the box within about three minutes.

If Postfjord could not add the box to a page, for example because the page is too big, the card says how many pages missed it after you press Save. Those pages send nothing until you publish them again.

To change the pixel later, type the new Pixel ID and paste its token. To keep the same pixel, leave the token field empty.

Send a Meta test event

1. In Events Manager, open your pixel and go to Test events. Copy the code that starts with TEST.
2. On the Meta Pixel card, paste it under Test events code.
3. Press Send test event.

Postfjord sends one made-up signup with that code, so it shows under Test events within a minute. Real signups never carry the test code. You can send 10 test events an hour.

Google Analytics

Postfjord sends signups to a Google Analytics 4 property, through Google's Measurement Protocol.

Before you connect Google Analytics

You need three things:

1. Your Measurement ID. In Google Analytics, go to Admin, then Data streams, and open your web stream. The Measurement ID starts with G-.
2. A Measurement Protocol API secret. In the same web stream, open Measurement Protocol API secrets and press Create. Give it a name, such as Postfjord, and copy the Secret value. If Google asks you to review its terms for user data first, read them and accept.
3. The address of your privacy policy. The same one as for the Meta Pixel, when you use both. The one box on your forms links to it.

Connect Google Analytics

1. Go to Pages. The Google Analytics card is near the bottom.
2. Paste your Measurement ID and your API secret.
3. Paste the address of your privacy policy.
4. Press Save and start.

Only the owner of the workspace can do this, and Postfjord asks you to sign in again first. The API secret is kept encrypted. The app shows only its last four characters. Your live pages show the new box within about three minutes.

To change the data stream later, type the new Measurement ID and paste its secret. To keep the same stream, leave the secret field empty.

Send a Google test event

Google takes any event it receives, even with a wrong API secret, and does not say whether it counted. So check it once:

1. On the Google Analytics card, press Send test event.
2. In Google Analytics, go to Admin, then DebugView.
3. Look for postfjord_test within a minute.

If it does not show, copy the Measurement ID and the API secret again and press Save. The test event is called postfjord_test, not generate_lead, so it never counts as a signup in your reports. You can send 10 test events an hour, for Meta and Google together.

When a signup is sent

A signup goes to Meta or Google only when all of this is true:

1. The person ticked the box on a form on one of your pages, and the box named that service.
2. They were not on your list before.
3. They signed up with the email address they typed on your page. If they change it on the next screen, nothing is sent.
4. Postfjord sent them the email to confirm, or it is waiting to go out.

A form on your own website never sends anything to Meta or Google, and neither does a page that does not show the box.

What Meta gets

For each signup:

• the person's IP address and browser,
• the page address with only its utm tags (everything else in the address is dropped),
• the time,
• and Meta's ad click id, when the visit came from a Meta ad.

Every signup asks Meta to apply Limited Data Use, Meta's setting for US state privacy laws.

What Google gets

For each signup, one generate_lead event with:

• the page address with only its utm tags, and those tags as the event's source, medium and campaign,
• the person's IP address, which Google uses for the country and city and does not keep,
• the person's browser,
• the time,
• a visitor id that Postfjord makes at random for this one event and never uses again,
• and the consent the box gave: ad user data granted, ad personalization denied.

Because the visitor id is new each time, Google cannot tie two signups, or a signup and a visit, to the same person. Each signup shows as a new user in Google Analytics.

To report on the utm tags, add source, medium and campaign as event-scoped custom dimensions in Google Analytics, under Admin, Custom definitions. Google only fills its own source and medium reports for visits its tag sees, and your pages run no tag.

What neither gets

Postfjord never sends an email address or a name to Meta or Google, in plain text or hashed.

Nothing is sent for a browser that sends Global Privacy Control, the setting that asks sites not to sell or share data, even with the box ticked. Bots are never sent either.

Sending stopped

If Meta says your token or Pixel ID is not valid, Postfjord stops sending to Meta and the Meta Pixel card says Sending stopped. Check both in Events Manager. Make a new token if you need to, paste it, and press Save. Sending starts again at once.

If Google refuses your data stream or API secret, the Google Analytics card says Sending stopped in the same way. Check both, paste the secret again, and press Save.

If Meta or Google does not answer five times in a row, Postfjord waits ten minutes before it tries again, so your signup form stays fast.

Each card also shows when the last signup went out and the last problem the service reported.

Remove the Meta Pixel or Google Analytics

Press Remove on the card and confirm. Postfjord deletes the settings for that service and stops sending to it at once. If the other one is still on, the box stays on your forms and names only that one. If neither is on, the box leaves your forms.

FAQ