Blip
← All guides

Get a push for every DataFast sale

DataFast shows your sales on a dashboard, but it does not ping your phone. DataFast cannot call Blip by itself, so the push comes from Stripe or from your own code. Both take a few minutes.

1

Create a Sales channel in Blip

Install the Blip iOS app, tap + to create a channel named Sales, and copy its key (it starts with blip_live_). The key is the only thing you need.

2

Using Stripe? Paste one URL into Stripe

DataFast gets your sales from Stripe. So the easy path is to have Stripe tell Blip too. Add a webhook endpoint in Stripe and paste this URL with your key in it. For sales, pick checkout.session.completed, plus invoice.paid if you sell subscriptions.

Each sale lands as "Payment received: $29.99" (or "Invoice paid") with the buyer's email under it. Tap it to open the event in Stripe. Failed payments, canceled subscriptions, and disputes come in as urgent pushes. Your DataFast setup stays as it is.

Stripe webhook endpoint URL
https://blipnotify.com/api/v1/hooks/stripe/blip_live_xxx

Webhook URLs work during the free trial and on Pro. The Stripe guide has more on the Stripe events Blip reads and how to send a test.

3

Other provider or your own server? Add one fetch

Selling through a provider DataFast does not link to on its own, or your own checkout? Then your code already sends each sale to DataFast with POST /api/v1/payments. Put one more call right beside it. DataFast wants amount (in whole units like 29.99, not cents), currency, and transaction_id. Blip only needs a title.

Node, where you record the sale
const post = (url, key, body) => fetch(url, {
  method: "POST",
  headers: { Authorization: `Bearer ${key}`, "Content-Type": "application/json" },
  body: JSON.stringify(body),
});

const sale = { amount: 29.99, currency: "USD", transaction_id: "order_123" };
await post("https://datafa.st/api/v1/payments", process.env.DATAFAST_API_KEY, sale);
await post("https://blipnotify.com/api/v1/notify", process.env.BLIP_SALES_KEY, { title: `New sale: ${sale.amount} ${sale.currency}` });

Add datafast_visitor_id to the DataFast call if you have it, so DataFast knows where the buyer came from. Blip does not need it.

4

Signups: send the same goal name to both

Same idea for goals. Where you send a goal to DataFast, send a push to Blip with the same goal name. Keep one name in one place, so what you see in DataFast and what buzzes your phone always match.

Node, right after you create the user
// Same post() helper as above.
const goal = "signup";
await post("https://datafa.st/api/v1/goals", process.env.DATAFAST_API_KEY, { datafast_visitor_id: visitorId, name: goal });
await post("https://blipnotify.com/api/v1/notify", process.env.BLIP_SALES_KEY, { title: "New signup", body: user.email, data: { goal } });

DataFast needs datafast_visitor_id and name for a goal. Use a different Blip channel for signups if you want sales and signups apart on your phone.

Why not a DataFast webhook?

Because DataFast does not have one today. Its alerts send email, nothing else, for now. So Blip listens to the same place DataFast does: Stripe, or your own code. A nice side effect: Blip never needs your DataFast API key.

Each channel takes up to 60 blips a minute, which is plenty for a launch day.

That's the whole setup.

Blip is free to try for 14 days, every feature included. After that it is $29.99/yr or $9/mo: see pricing.

Download on the App Store

More guides