You can send your Feedier surveys from your own email or SMS tool (Brevo, Mailchimp, HubSpot, Salesforce Marketing Cloud, etc.) instead of from Feedier. Simply insert the survey link in your message and add your contact information as URL parameters.

If you want a custom URL, and have your domain instead of "feedier.com" you need to follow the instructions here.

From your survey's Share page, copy the Survey link. If you have set up a custom domain, use that link instead: it works exactly the same way.

Any parameter appended to the link is automatically saved as an attribute on the feedback received.
​
A few rules for the URL itself:
- The first parameter starts with ?, the following ones are joined with &.
- With a custom domain, the ? goes directly after the domain.
- {{contact.email}} etc. are placeholders to replace with your tool's own personalization syntax (Brevo uses {{ contact.EMAIL }}, Mailchimp *|EMAIL|*, HubSpot {{ contact.email }}…).

Use your tool's personalization tags to fill in the values:

→ Every other parameter (store_code, order_id, customer_id…) becomes an attribute. Names are normalized to lowercase with underscores (Store Code → store_code).

→ A few attributes need to be setup by default and have to be used in the URL so that Feedier can correctly setup and send the survey:

- email will be used by Feedier as the email the survey will be sent to.
- About multilingual surveys, you need to add the attribute locale (e.g. fr, en, de) forces the display language of the survey.
​
⚠️ URL-encode your values (spaces, accents, &, #): most tools do this automatically in their personalization tags. Check with a test send.
​
⚠️ Some names are reserved by Feedier and will not be saved as attributes: phone, preview, step, completed, feedback_id, satisfaction, subject, no_header, organization. For a phone number, for example, use another name such as mobile or telephone.

No. When a feedback comes in with a URL parameter, Feedier looks up the matching attribute in your organization and creates it automatically if it doesn't exist (the label is derived from the name: store_code → "Store Code"). Empty values are ignored, as well as the reserved names listed above.
​
Two things to keep in mind:
- Naming consistency matters: names are normalized (Store Code, store-code and store_code all become store_code), but shop and store_code would create two separate attributes. If your organization already has an attribute for that data, reuse its exact name.
- Creating attributes upfront is still a good practice if they need a specific visibility (hidden, visible to assigned users only) or must be flagged as sensitive. Otherwise the new attribute is created public by default and could expose personal data in reports until an admin adjusts its settings (Menu → Attributes).

Send yourself a test from your tool, click the link and answer: the feedback should appear in Feedier with the expected attributes.
​
​What changes compared to a Feedier campaign
- Sending statuses (delivered, clicked, bounced…) and the Pushes report are not available: deliverability tracking is done in your tool.
- Unsubscribe management and the anti over-solicitation rule (12h) are handled by your tool, not by Feedier.
- If you want to keep Feedier's tracking while triggering sends from your own system, use a Feedier campaign triggered via the API instead (see the section above).