Once a form is saved, you can put it on your website, link to it from emails and social posts, or send personalised links.
On the Forms page, click ⋯ on the form and choose Get code and links. In the builder, go to Form settings → Settings → Sharing: copy the code there, or click All options. Either way, the Share this form page opens, laid out by what you want to do, each with a Copy button.
Before you share a form, check that Public-facing form is ticked (Form settings → Settings → Security). If it isn't, or the form is switched off, the page warns you at the top. If the form's payment provider takes people to its own page to pay (such as Windcave or Flo2Cash), the page says so too.
Credit gifts to a campaign (optional)
At the top of the page you can choose a Campaign and GL code. Leave them as The form's own to use the form's settings. Choose them to use a general form for one campaign, for example a link in an email appeal that goes to your general donation page. Everything below on the page (the code and the links) then includes them. See How a campaign in a link is used below.
1. Put it on your website
Copy the code and paste it into your web page where the form should appear, or send it to whoever looks after your website. Copy a message for my web developer copies the code with a short note explaining what it does.
The form fills the width of the space you put it in, up to the content width set in its style, and adjusts its height as people move through it, so there are no scroll bars inside a box.
2. If your website won't accept that code
Some website builders and content systems remove code like the above, and some organisations don't allow outside scripts. Use the second code instead. The form fills the width the same way but appears at a fixed height and can't adjust it: make it taller if the form gets cut off.
3. Share a link
The form's own web address, for emails, social posts, QR codes and text messages, or a website builder that only asks for a web address. No code is needed on your website. Open the form shows it in a new tab.
It looks like forms.vega.works/your-organisation/your-form-name. The last part comes from the form name.
Personalise it for each contact
A personalised link (with a contact's Vega ID) recognises the person. Depending on the Contact details section's settings, they see either a short summary of who they're filling in as, or every field already filled in. They can always choose Not you?, which clears their details. See Collecting contact information and answers.
In emails, use a merge tag so each person gets their own link. The page shows each one ready to copy, both for a link to the page on your website where the form is and for a link to the form itself:
| Merge tag | What it adds | Example |
|---|---|---|
| #URLParameters# | The contact and, when the email is part of a campaign, that campaign. Emails sent from Vega only. A campaign chosen at the top of the page isn't added: the email's own campaign is used | www.your-website.org/donate?#URLParameters# |
| #GUID# | Just the contact | www.your-website.org/donate?contactguid=#GUID# |
From another email platform, use its merge field for the contact's Vega ID instead.
Warning: Each personalised link opens that person's details. Send it only to them – don't post it on a website or social media, and never put a real contact's Vega ID into the code on a public web page.
How a campaign in a link is used
A campaign in a link or the website code (including the one #URLParameters# adds) replaces the form's default campaign and its pathway rules. A donor's choice in a Designation section still wins, and memberships and tickets keep their own campaigns.
The campaign or GL code has to be one of your organisation's own, and active. Anything else is ignored and the form's own campaign and GL code are used.
Details for developers
Folded away at the end of the page. The website code takes these details:
| Detail | What it does |
|---|---|
| data-form-id | Required. The form's ID |
| data-contact-guid | Personalises the form for one known contact (their Vega ID). Only use it on a page that a single person will see |
| data-campaign-id | Files submissions under a particular campaign, instead of the form's default |
| data-category-id | Files submissions under a particular GL code, instead of the form's default |
| data-amount | Pre-fills the donation amount, e.g. 50. It selects that preset amount if there is one, otherwise it fills in Other |
| data-frequency | Sets the frequency by name, e.g. Monthly. People can't change it, so use it for a page that is only for one kind of giving |
| data-base-url | Where the form is hosted. Only needed in unusual setups |
Links take the same details: contactguid, campaignId, categoryId, dtnAmt (the amount, e.g. dtnAmt=50) and freq (the frequency, e.g. freq=Monthly). They work in any combination of capital and small letters.
The website code also reads them from the address of the web page it's on, as the old widgets did. So a link to your own page, such as www.your-website.org/donate?campaignId=123, passes the campaign to the form on it. The older names still work: cID for the campaign, ctID for the GL code, xlnse3 for the contact, dtnAmt for the amount and freq for the frequency. A detail set on the code itself wins over the page's address.
Renaming a form
The form ID never changes, and the website code (both kinds) uses it, so renaming a form doesn't break forms on your website.
The link changes when you rename a form, because it's based on the name, but links using the earlier name keep working: the form opens and shows its current address.
Payments on forms on your website
Card payments, Google Pay and Apple Pay all work inside a form on your website. With payment providers that take people to their own payment page (such as Windcave or Flo2Cash), people are taken there and brought back afterwards.
Comments
0 comments
Please sign in to leave a comment.