Before you start
Anyone who sets this up needs a Tracker login and access to Tools & Settings. Tracker's guide does not name a role or plan for the API. If you can't see Security Settings, ask your Tracker database administrator.
The API token belongs to the Tracker user who creates it. Metaintro sees jobs and adds candidates as that user, so use an account that can see the jobs you want to connect.
Tracker's API is in beta. It is open to Tracker customers without a partner agreement.
You will paste two things into Metaintro:
Your data region: us, ca or global
Your Tracker API token
Create the credential in Tracker
These steps follow Tracker's guide, Tracker API Authentication.
Log in to Tracker. Look at the web address in your browser and note where your database is held: the US, Canada or somewhere else.
Go to Tools & Settings > Security Settings > API.
Copy your existing token, or generate a new one.
Only one token works at a time. If you generate a new token, the old one stops working. Anything else that uses the old token, including Metaintro, must be given the new one.
Connect in Metaintro
In Metaintro, go to Settings > Integrations.
Choose Tracker.
In Data region, type us for a US database, ca for a Canadian database, or global for anywhere else.
In API token, paste the token you copied from Tracker.
Select Connect.
Metaintro checks the token by reading your jobs. Then you can map jobs, set rules, preview and go live.
What Metaintro sends and reads
Metaintro only sends people who chose to share their profile with you for one of your jobs.
For each person, Metaintro:
Looks for a Tracker candidate with the same email address, as their main or second email. If it finds exactly one, it uses that candidate instead of creating a new one.
Otherwise creates a candidate with their name, email and mobile number, with the source set to Metaintro.
Adds them to the job's shortlist at your first Shortlisted status (or Applied, if you have no Shortlisted status), with the placement source set to Metaintro.
Attaches their résumé as the candidate's main résumé, when they have one.
Adds a note to the candidate and the shortlist entry with a link to their proof card.
Metaintro checks each person's shortlist status in Tracker regularly. Tracker does not tell Metaintro about changes as they happen. Metaintro reads your status types like this:
Shortlisted or Applied: no change yet.
CV Review: contacted.
Interview: interviewing.
Offer: offer.
Working or Complete: hired.
Rejected: not selected.
A status named "withdrawn": withdrawn.
When you change a person's stage in Metaintro, Metaintro moves their shortlist entry in Tracker to a matching status, if you have one.
Limits
Tracker's API is in beta, so Tracker may change it.
Generating a new token in Tracker disconnects Metaintro until you paste the new token.
Tracker allows about 100 API calls a minute. Metaintro stays under that, so large job lists and stage checks take a little time.
Stage changes show up in Metaintro after the next regular check, not instantly.
Metaintro can only mark someone as withdrawn if you have a shortlist status whose name says withdrawn.
If two or more Tracker candidates have the same email address, Metaintro does not guess which one is right and does not send that person.
If something goes wrong
The token is rejected. Check you copied the whole token and picked the right data region. If someone generated a new token since, paste the new one.
Jobs or candidates are missing. The token's user may not have access to them. Use a token from a user who can see those jobs.
Tracker says too many requests. Metaintro waits and tries again on its own. If other tools use the same Tracker account heavily, updates may take longer.
The résumé or note is missing. Tracker refused to save it. Contact Metaintro support with the person and job, and we will look into it.