Link tags, sales and results

Link tags

Every link Postfjord sends people to gets UTM tags: the links in your automations, in your emails and on your landing pages. Your own analytics, like Google Analytics, Shopify or your booking system, then shows the visits and sales that came from Postfjord.

A link to your class page becomes, for example:

`` https://yourstudio.com/classes?utm_source=postfjord&utm_medium=dm&utm_campaign=k3Fq9zLm2a ``

• utm_source is always postfjord.
• utm_medium says where the link was: dm for an automation, email for an email, page for a landing page.
• utm_campaign says which one: the email's code, the page's address, or the short link's code in an automation. An email's name stays private.

Tags that are already in your link stay as you wrote them. Links to profiles, posts and videos on other platforms stay clean on your pages, since their apps show the address as it is. The tags never name the person who clicks. A booking link or a Stripe payment link from an automation also carries a random code, so the booking or purchase can be counted for that automation.

The switch is under Settings → Apps → Link tags. Only the workspace owner can turn it off. A link to a booking page keeps its tags either way, because that is how a booking is counted (see Count your bookings). A new setting reaches your automations and emails within a minute. A landing page gets it the next time you publish it.

Sales from Stripe

Connect your Stripe account, and Postfjord counts what your Stripe payment links sell: per automation, per email and per landing page.

1. In Stripe, open Developers, then API keys, and press Create restricted key.
2. Call it Postfjord. If Stripe shows ready-made permission templates, skip them and pick the option to set permissions yourself. Search for webhook, set Webhook Endpoints to Write and leave everything else at None. Press Create key.
3. Copy the key (it starts with rk_live_). In Postfjord, paste it on the Stripe card under Settings → Apps → Bookings and sales and press Connect.

The key can only manage webhooks, so it cannot move money or refund. Postfjord uses it to add its own webhook to your Stripe account and to remove it when you disconnect or delete the workspace, and keeps it encrypted. A key that starts with rk_test_ connects in test mode, so you can try it with Stripe's test cards first. Test purchases show on the Stripe card only, never in your numbers.

Then put a Stripe payment link (buy.stripe.com) in an automation, an email or a landing page. Postfjord adds a code to the link when someone opens it, and Stripe sends the code back with the purchase. That is how a sale counts for the automation, the email or the page that sent the buyer:

• Automations show Sales with the amount, next to Clicks and Bookings.
• Email reports show Sales for that email.
• Landing pages show Sales on the page's Numbers tab, since you connected Stripe.
• The Results card on the dashboard shows the month's sales.
• The buyer gets the tag Customer when they are a contact, which can start an email automation.

A purchase without the code, for example from a link someone saved, still counts for an automation when the buyer is a contact with the same email address and tapped a payment link in that automation in the week before. A refund takes its amount off again, and a full refund takes off the sale.

Postfjord keeps the amount, the currency and what sent the buyer, never their name or email address. Payment links on your own domain cannot get the code and are not counted per automation.

Results on the dashboard

The Results card on the dashboard shows the bookings and sales that came in this month and the automations that brought the most. Until a booking system or Stripe is connected, the card has a button to connect one. You can move or hide it like every other card.

FAQ