CRM integrations and API: data sources, CMS and notifications
Integrations and API is the part of CRM development at Best Boost Partners that connects the CRM to the services your team already uses. Data from Google Search Console, Google Analytics, rank trackers and link indexes arrives in the CRM on a schedule. Approved texts go to the CMS of your sites, notifications go to a messenger, and payments are exported for accounting. The CRM also gets its own documented API, through which your scripts and other systems read and create records.
What exactly do we connect to the CRM?
Google Search Console and Google Analytics
Clicks, impressions, positions and visits are loaded on a schedule and attached to the project, the domain and the page. Google Search Console returns data with a delay and within its own limits, so the CRM shows the date up to which the data has been loaded.
Rank trackers
Positions from the rank tracker your team uses are loaded through its API and linked to pages and queries in the CRM. The CRM keeps the history, so a change in positions can be compared with the dates of texts and links.
Link indexes
Data from link indexes such as Ahrefs and Majestic is requested for donors and for your own domains. In the donor card the metrics on the date of the check stand next to the price and the placement history.
Messengers and notifications
The CRM sends notifications to a messenger or by email: a new task, a deadline that is close, a text waiting for approval, a link that has disappeared. Each user chooses which events to be told about.
Publishing to the CMS
An approved text is sent from the CRM to the CMS of the site, for example WordPress or MODX, as a draft or as a published page. The CRM saves the URL and the publication date in the text record.
Exports and the CRM’s own API
Payments are exported in the format your accountant or accounting software accepts. The CRM’s own API, with keys and access rights, lets parsers, reports and other internal tools read and create records.
What do you get from integrations and the API?
- Configured connections to the agreed services, each with its own schedule and a log of runs and errors.
- A settings screen where the administrator replaces keys and tokens without a developer.
- API documentation: methods, fields, request examples and the rules for issuing keys.
- A table showing which field of the CRM is filled from which source and how often the field is updated.
When are integrations and an API needed?
- Specialists copy positions, traffic and link metrics into the CRM or a spreadsheet by hand.
- Approved texts are pasted into the CMS manually, and the publication date and the URL get lost.
- The team learns about an overdue task or a lost link by chance, because nobody receives a notification.
- You already have scripts and parsers, and they need a place to write their results.
Frequently asked questions
Which services can the CRM be connected to?
The CRM can be connected to any service that has an API or a regular export: Google Search Console, Google Analytics, rank trackers, link indexes, messengers, the CMS of your sites and accounting software. The exact list is fixed in the specification. For a service without an API we consider file import as a replacement.
What happens if an external service changes its API or stops responding?
Each integration is a separate module, so a failure of one service does not stop the CRM. A failed request is written to the error log and repeated later, and the administrator receives a notification. If a service changes its API, a developer has to update the module, and the documentation describes where this is done.
Do we need our own accounts with rank trackers and link indexes?
Yes, the integrations work through your own accounts and API keys in those services. The keys are stored on your server, and the subscription and the request limits of each service remain yours. Before development starts we check which data each plan of the service gives out through the API.
Tell us about the project
Fill in what you already know. Blank fields are fine: we will clarify the rest in conversation.
Brief sent
Thank you. We will reply within one working day.
Preview mode: the form handler is not connected yet, so nothing was sent.