Many integrations with classic CRM are templates and require further development. Depending on the customer's requirements, you may need additional fields when submitting leads and additional options when loading statuses.
Bitrix
The integration creates a "lead" entity, checks its status before converting it into a deal. After converting into a deal, the lead is considered accepted and the statuses of the deal are checked.
Before integration, ask the advertiser for the URL for the crm.lead.add function. It will look like this:
https://crm.domain.com/rest/1234/abcde/crm.lead.add.json
Settings for the integration utility:
- Domain: domain like crm.domain.com from the API url.
- User: value in place of 1234 from the API url.
- API: value in place of abdce from the API url.
Parameters used:
- crm - product ID from CRM, which can be added to the lead after it is created. Optional parameter.
After running the utility, you may need to add additional fields to the submission and statuses to the lead check. Check with your advertiser for this information.
E-Autopay
Settings for the integration utility:
- User: symbol user ID.
- API: user token.
Parameters used:
- eauto - main product identifier.
InHouse
Settings for the integration utility:
- API: token for sending orders and checking statuses.
- Subdomain: the xxx part from the project domain xxx.weirdstuff.io.
- Parameter: the name of the parameter for the product code.
LeadVertex Admin
Integration with LeadVertex on behalf of the administrator. Requires extended API activation.
Settings for the integration utility:
- Subdomain: part xxx from the xxx.leadvertex.ru project domain. Sometimes you need to work with many projects from one supplier. In this case, it is recommended to specify the value {ofp:lvx} in this field and use the offer parameter lvx to specify the project address.
- API: key from advanced API settings. Should be the same for all projects.
- Parameter: the name of the parameter for the item ID. Both offer parameters and nested product parameters can be used. You can leave the default value.
- User: ID of the webmaster to which the lead is linked. Can be left blank to not link leads to a webmaster.
Default parameters used:
- lvid - identifier of the main or nested product.
- lvx - character project identifier.
Once configured, you may need to add additional1-15 parameters when submitting a lead, if the advertiser needs them.
LeadVertex CallCenter
Integration with a call center based on LeadVertex. Requires admin access and advanced API activation.
Settings for the integration utility:
- Subdomain: part xxx from the xxx.leadvertex.ru project domain. Sometimes you need to work with many projects from one supplier. In this case, it is recommended to specify the value {ofp:lvx} in this field and use the offer parameter lvx to specify the project address.
- API: key from advanced API settings. Should be the same for all projects.
- Parameter: the name of the parameter for the item ID. Both offer parameters and nested product parameters can be used. You can leave the default value.
- User: ID of the webmaster to which the lead is linked. Can be left blank to not link leads to a webmaster.
Default parameters used:
- lvid - identifier of the main or nested product.
- lvx - character project identifier.
Once configured, you may need to add additional1-15 parameters when submitting a lead, if the advertiser needs them.
LeadVertex Webmaster
Integration with LeadVertex on behalf of the webmaster. The advertiser must give you access to sending leads and checking extended statuses.
Settings for the integration utility:
- Subdomain: part xxx from the xxx.leadvertex.ru project domain. Sometimes you need to work with many projects from one supplier. In this case, it is recommended to specify the value {ofp:lvx} in this field and use the offer parameter lvx to specify the project address.
- User: webmaster ID from API settings. Must be the same for all projects.
- API: key from API settings settings. Must be the same for all projects.
- Parameter: the name of the parameter for the item ID. Both offer parameters and nested product parameters can be used. You can leave the default value.
Default parameters used:
- lvid - identifier of the main or nested product.
- lvx - character project identifier.
Once configured, you may need to add additional1-15 parameters when submitting a lead, if the advertiser needs them.
LP CRM
Settings for the integration utility:
- Subdomain: the xxx part from the project domain xxx.lp-crm.biz.
- API: user token.
- Parameter: the name of the parameter to store the product ID.
After integration, it may be necessary to agree on the list of order statuses.
OneHash
Settings for the integration utility:
- API: token for sending orders and checking statuses.
- Subdomain: the xxx part from the project domain xxx.onehash.ai.
- CHANNEL: channel_id field value.
- Parameter: the name of the parameter for the item ID.
PingDelivery
Settings for the integration utility:
- Username and password: login data provided by the customer
After integration, it may be necessary to agree on the list of order statuses.
RetailCRM
Settings for the integration utility:
- Subdomain: the xxx part from the project domain xxx.retailcrm.ru.
- API: user token.
Parameters used:
- rts - symbol store identifier.
- rtid - product ID in the store from the parameter offer.id.
After integration, it may be necessary to agree on a list of extended order statuses. Caution: on this CRM, there are advertisers who enter the status of orders in processing in the group of approved orders. Be sure to check the load of statuses after setting up!
ReWorker
Settings for the integration utility:
- User: ReWorker Client ID.
- Shop: shop ID for sending orders.
Default parameters used:
- rwk - product ID (SKU).
Scaleo
Settings for the integration utility:
- Domain: API-domain line api.domain.com.
- API: user token.
- Parameter: the name of the parameter to store the goal ID.
Telesales
Settings for the integration utility:
- User: webmaster or advertiser ID.
- API: token for sending orders and checking statuses.
Default parameters used:
- rwk - product ID (SKU).
Telesales CallCenter
Same as Telesales, uses loading the order content in a comment.
UpsaleMe
Settings for the integration utility:
- API: token for sending leads.
- Ключ: token for checking statuses.
Parameters used:
- upsaleme - stream identifier for sending leads.
- mcc - product ID to download shopping cart contents.
After integration, you need to set up offers: add the same nested products to them as those created on the UpsaleMe side and specify the ID in them in the mcc parameter.