Failed leads API injection

The “Failed Leads API injection” feature allows you to track leads that were not successfully injected into your CRM.

When a lead is rejected, the system automatically generates an entry in the logs; it provides detailed information about the failed injection; and includes the reason why the injection failed.

Why does leads injection fails

There are multiple reasons for a lead coming via API to fail being injected in aNinja. Here are the reasons that we log in Settings > logs. Leads injection could fail due to:

  • Duplicate Emails
  • Missing required fields (contact_name)
Failed leads API injection due to duplicate Emails

In Settings > Global Settings, if the following rule is enabled,

“Do not add new Leads via api if Lead with similar email already exists (avoids duplicates)”

when a lead is added via API, the system first checks if the lead already exists in the CRM.

It compares the email address of the new lead with the existing leads in the system.

If the system identifies an existing lead with a similar email address, it does not add the new lead to avoid duplication. Subsequently, it generates an entry in Logs, providing the reason of the failed lead injection.

Failed lead API injection due to missing required field

The contact name is the only required field for a successful lead creation. And the system creates the lead in reference to the contact name and saves the lead data.

If the lead data coming through API is missing the contact name, it does not create a new lead; and it generates an entry in Logs with the reason of failed lead injection.

Accessing the Failed leads API injection Logs

  • Click on “Failed leads API injection” from the toolbar

Failed leads API injection due to duplicate emailsIn this table, you can view:

  • ID: A sequential number
  • Reason: The reason for which the lead failed to inject
  • Data: The source of the lead that failed to inject
  • Created: The date & time this record was created – failed to inject.

By providing clear and detailed information about rejected leads, you can quickly identify the failed leads injection and address the issue.

aNinja Activities Logs

It’s important to have a clear understanding of all the activities and interactions that occur on your aNinja account. aNinja provides a helpful solution in the form of activity logs reports, allowing you to conduct audits whenever necessary.

Specifically, the logs report feature provides a comprehensive overview of all incoming and outgoing calls, emails, and texts, and the triggers you’ve launched. Additionally, you can easily view the failed leads API injection.

Accessing aNinja Activities Logs reports

Activities Logs

  • Calls
    • You can see the details of the incoming and outgoing calls, including the lead ID, duration and date of the calls.
    • You can also listen to the recordings of the conversations.
  • Emails
    • Here are saved all the details on the incoming and outgoing emails, including the sequences and their statuses.
  • Texts
    • You can see the details of the incoming and outgoing texts, including the sequences and their statuses.
  • Audit Log
    • As an admin user, this option allows you to see the activity of the users in searching for leads using smartlists or from the top navigation bar, and the lead view that the users opened.
  • Failed leads API injection
    • You can identify any leads that failed to import into your aNinja account via API for duplicate emails.

Merging leads

When you create or import new leads into your aNinja account, if they already exist in the system based on the email or phone number, they will be detected as duplicates by our duplicate search.

However, you may want to merge those duplicates into one lead file to avoid bloating your system. Merging leads could be also a good solution to avoid contacting the same lead several times.

Please note that when you merge leads, you can no longer retrieve the merged lead.

Merging Leads

You can access the merging feature from 2 different places in aNinja: From the lead view, and from Settings.

  • Lead view:
    • When on the lead view, scroll down to the end of the page and click on merge.
    • Then, choose a destination lead to merge this lead into. Immediately, this lead will be deleted after the system merged into the destination lead.
  • On the left sidebar > Settings > Data clean-up
    • Then, choose the method you want to use for your search to merge through (by email / by phone).Merging leads
    • Locate the leads you want to merge.
    • Lastly, click on the ID of the lead you want to merge. The system deletes this lead after it merged it into the lead you want to keep.

What are the fields that get merged?

What’s merged and appended into the lead file you’re keeping includes:
– Contacts
– Opportunities
– Emails
– Tasks
– Address
– Texts
– Calls
– Notes
– Triggers
– Chat conversations
– Workflows
– Custom fields

Note! All the email or text sequences of leads that are being merged are stopped. Therefore, only the sequences for the remaining lead stay active.

Duplicate Data Cleanup

Sometimes duplicate data is useful, sometimes it just makes it harder to understand your data. Perform a duplicate Data Cleanup more often to merge the relevant duplications as you don’t want to send multiple emails / texts to the same lead.

Using Data Clean-up

Use the data clean-up to find and highlight duplicate data. That way you can review the duplicates and decide if you want to merge them.

  • In the left sidebar, click on Settings > Data Clean-up
  • Choose to see the duplicates based on Email Or Phone
  • Merge the duplicates in a single lead