Say where a contact came from
Contacts you add over the API can now carry where they came from and the customer's address, and you can build an audience on it.
Released 19 August 2026
When your website, shop or back office adds someone to Contacts, it can now say where they came from — and save their address at the same time. Until now everything added that way looked the same: "Via API", with nowhere to put the address you had already collected.
What is new when you add a contact over the API:
- Where they came from. Name one of the shops you sync — Shopify, WooCommerce or qTap.store — and the contact carries that shop's badge. Or use a word of your own, like "landing-page" or "crm", and it shows as its own badge in the contacts list.
- It sticks. The origin is set when the contact is first created and is never rewritten afterwards, so you can always see where someone actually came from — even after they have been updated a hundred times.
- Their address. Street lines, city, state, PIN code and country, plus who receives at the address, a label of your own ("Home", "Warehouse 2"), whether it is for billing or delivery, and a map pin. Everything is optional — send what you know.
- Nothing is overwritten. Addresses are added to what the customer has already shared with you, so an address they sent over WhatsApp themselves is never replaced or lost. Send the same one twice and it will not be duplicated.
You can also build an audience on where people came from: set a rule's field to source on the Segments page — for example, everyone your shop sync created, or everyone from one landing page.
Contacts added by hand in the console, by import, or by messaging someone new are unchanged.