Leads are created or updated automatically, allowing your recruitment and admissions teams to work from a single, up‑to‑date database.
How it works
The integration uses Full Fabric Forms endpoints.
Keystone is configured to send each new lead or application as an HTTP POST to a specific Full Fabric form endpoint. The form’s field configuration and mapping rules determine how the payload is transformed into a person record, application and attached programme/intake information.
Key benefits:
Real-time lead ingestion from Keystone into Full Fabric
Unified lead database across all channels
Consistent source and campaign tracking for reporting
Automatic triggering of nurture campaigns and tasks
Prerequisites
You’ll need:
Full Fabric admin access to set up forms and endpoints
Keystone account access with permission to configure lead delivery (API/webhook)
Agreement with your Keystone account manager on:
Payload format and fields
Delivery method (direct POST/webhook)
Any authentication requirements
A mapping document linking Keystone fields (programme ID, study level, intake, campus, source tags) to Full Fabric form fields
Getting your Full Fabric form endpoint
Go to Apps > Forms in Full Fabric.
Create a dedicated form (e.g. “Keystone Lead”) or open an existing lead form.
Ensure it contains all fields you expect Keystone to send (name, email, phone, programme, level, intake, consent, source, etc.).
Publish the form.
Open the form’s Endpoint or Integration settings.
Copy the endpoint URL for use in Keystone’s lead delivery configuration.
Configuring Keystone
Share the endpoint URL
Provide the Full Fabric form endpoint URL to your Keystone contact.
Confirm payload structure
Ask Keystone for a sample payload and verify the fields align with your Full Fabric form field names.
Adjust field names on your form or mapping rules if needed.
Programme and intake mapping
Ensure Keystone sends stable programme identifiers (codes, IDs or slugs).
Map these identifiers to your Full Fabric programmes and intakes.
Decide how to handle multi‑programme or multi‑intake leads, if applicable.
Consent and source
Confirm that Keystone includes consent fields where required.
Include a field in your form to capture Keystone as the source or campaign, and map the corresponding payload field.
Authentication (optional)
If you require a token or shared secret, configure Keystone to include it in each request and configure validation in Full Fabric or your integration layer.
Testing the integration
Ask Keystone to send several test leads with distinguishable test names and addresses.
In Full Fabric, open the form’s Submissions list and verify that the tests appear.
Check People to confirm that corresponding records are created or updated.
Verify:
Correct personal details (name, email, country, etc.)
Correct programme and intake assignment
Source/campaign fields show Keystone as expected
Automations (emails, tasks, workflows) run correctly for these leads
If test leads don’t appear:
Confirm the endpoint URL Keystone uses matches what you provided.
Ensure the form is published.
Ask Keystone whether they see any errors when posting to the endpoint.
After go‑live
Once you start receiving live leads:
Monitor daily to ensure volume and data quality are as expected.
Use Full Fabric lists and dashboards to track Keystone‑sourced leads, application rates and conversions.
Adjust your Keystone campaigns and forms based on performance insights from Full Fabric.
Keep your mappings updated when:
You add or remove programmes on Keystone.
Programme codes or labels change.
You introduce new fields (e.g. new consent or segmentation fields).
Troubleshooting
Issue: Keystone leads not appearing
Double‑check the endpoint URL in Keystone.
Confirm whether Keystone sees delivery errors.
Verify the Full Fabric form is still active and published.
Issue: Missing or wrong field values
Compare a sample Keystone payload with the Full Fabric form configuration.
Fix any mismatches in field names or types.
Re‑test after mapping changes.
Issue: Duplicates for returning leads
Ensure email or another unique identifier is always present.
Configure the form to update existing records when the identifier matches.
Review any custom deduplication rules.
Issue: Leads linked to incorrect programmes/intakes
Confirm the identifiers Keystone sends match those you expect.
Check the programme/intake mapping configuration.
Correct and re‑test with a new sample lead.
Getting support
For support, share:
Example lead email and submission time
Name of the Full Fabric form used
Endpoint URL (redacting any secrets)
A sample payload from Keystone, if possible
This allows the support team to quickly replicate and diagnose the issue.