Now live on ZidStart free

Industries

Health and supplements

A repeat order under strict ad policies: what you send has to be enough to match on and free of any raw identifier.

The order shape

Three properties that explain everything below

A sector here is defined by the shape of its orders rather than by a claim about its merchants: how large the basket is, how long the gap between click and order runs, how much is cancelled and returned, when it is paid, and whether the customer comes back.

  1. The purchase repeats at regular intervals, so the signal that matters is the repeat, not the first order.

  2. Platforms scrutinise this sector more, and a rejected event costs more here.

  3. Customer data is sensitive, and exactly what leaves the store has to be known.

Use cases

2 cases in this sector

Each case names what actually goes wrong, then what Raasid does about it step by step, then where you see it on screen. No promised result: the result belongs to your store.

  1. Strong matching without a raw identifier

    What happensGood matching needs identifiers, and raw identifiers must not leave the store. The common answer is to send less, which is exactly what weakens the matching.

    MechanismEmail and phone are normalized and then turned into a SHA-256 hash before they leave your store, and the hash cannot be reversed. The platform matches the hash against its own database without ever seeing the text.

    You see it inThe match-quality score with a blunt verdict beside it, and the state of each identifier on its own.

  2. The pixel failed at checkout

    What happensThe purchase completed in your store and was written to its database, but the purchase event never reached the platform. The campaign looks like a loss when it is not.

    MechanismRaasid recovers confirmed purchases straight from the store's database, so the event is built from what actually sold rather than from what the browser managed to send.

    You see it inThe coverage share before and after recovery, and the orders that arrived with no source.

What carries the weight here

The capabilities, ranked for this sector

This list is counted from the cases above: a capability two or more cases need is core here, and one a single case needs depends on your situation. The capabilities themselves are available in every sector.

Core in this sector

    Depends on your situation

    6 of 19 capabilities appear in this sector's cases. The rest are available, but no case here names them.

    Questions in this sector

    Is Raasid different from sector to sector?

    No. It is one product and all 19 capabilities are available to everyone. What differs is which ones carry the weight: in Health and supplements, 0 do, because two or more of the sector's cases need them.

    My store is in this sector but on a different platform

    The sector does not decide the connection. 3 connectors work today: Zid, Salla, Shopify. The rest are in development with no date, and the platforms page states where each one stands.

    Do you send to all my ad platforms?

    Yes, 4 platforms from a single install: Meta, TikTok, Snapchat, Google Ads. Each channel has its own settings and its own delivery record.

    Do you have numbers from stores in my sector?

    No, and we will not show figures we do not have. What you find here are mechanisms: what is read, what is sent and what appears on screen. The effect depends on your store and your campaigns, and it is yours to measure from your own dashboard.

    Is this your situation?

    Install the app and start, or message us and we'll walk through your sector's cases with you.