Use case

How iAdvize orchestrates its intent signals with Cargo, Salesforce, and lemlist

How iAdvize combines Cargo, Salesforce, Similarweb, FullEnrich, and lemlist to collect, enrich, and activate its commercial signals.

Yves Le GrouyerYves Le GrouyerChief Marketing Officer, iAdvize15 November 20264 min read
iAdvize, en interne

iAdvize develops an AI Shopping Assistant for retailers and e-commerce businesses. The company has about 150 employees and supports just over 400 clients in Europe and the United States.

Yves has been working at iAdvize for eight years and currently leads the marketing team. He previously participated in the creation of the data and CRM teams, which keeps him very involved in a rather operational topic: how to identify the right accounts and transform available data into signals that are truly usable by salespeople?

To achieve this, iAdvize has built a workflow around Cargo, Salesforce, Similarweb, FullEnrich, and lemlist.

Why is traditional B2B data not enough for iAdvize?

The usual segmentation criteria, such as the number of employees or revenue, are not really enough to measure a retailer's potential for iAdvize. The team therefore seeks to know their web traffic, the technologies they use, or certain events likely to signal a business opportunity.

This is also why iAdvize does not necessarily seek to centralize all its data on a single platform.

Yves cites Clay as an example of a tool that can directly meet the needs of companies whose segmentation criteria are more standard. iAdvize preferred to aggregate several specialized sources, chosen based on the information sought.

How does iAdvize use Cargo with Similarweb, BuiltWith, and Apify?

Yves Le Grouyer describes Cargo as a kind of “Zapier or n8n specialized in go-to-market.”

The tool serves as an orchestration layer between the different sources used by iAdvize:

  • The company is a direct client of Similarweb for traffic data. Yves currently considers it his reference for this need.
  • BuiltWith is used more occasionally to identify the technologies deployed by targeted companies.
  • Apify and some databases from Data.gouv are also part of the sources exploited in the workflow.

Cargo retrieves this different information and then redistributes it to Salesforce, HubSpot, and other relevant tools.

The interest is quite simple: to be able to choose the best source for each type of data rather than relying entirely on a single database.

How does iAdvize organize its enrichment waterfall with FullEnrich?

The enrichment of contacts illustrates this logic well.

iAdvize mainly uses FullEnrich, but no source can systematically find all the information.

The team operates in a cascade: when data is not available from a primary provider, another source can take over.

According to him, some of these sources can also be queried by consuming credits via Cargo, without necessarily subscribing directly to each provider.

iAdvize can thus maintain a few main providers for its recurring needs and occasionally call upon other databases via Cargo when necessary.

Collecting more data is only useful if salespeople can actually use it. Everything that is useful is fed into Salesforce, which serves as the company's business source of truth.

Marketing ensures that signals are correctly relayed. Their importance then determines the speed at which they must be processed by the sales teams: a very strong signal should prompt a faster reaction than an indirect signal.

Why did iAdvize abandon a lead scoring system that became too complex?

iAdvize had previously built a particularly advanced scoring model.

The system aggregated numerous criteria to try to precisely determine the value of a lead. In hindsight, Yves considers that this sophistication was disproportionate to the volumes actually processed.

Above all, the team risked dedicating a lot of energy to perfecting its model while missing simple signals that should have been addressed immediately.

iAdvize therefore started again from a few much more direct events, notably site visits and certain engagements on LinkedIn. The priority was no longer to calculate the best possible score, but simply to ensure that the most obvious signals reached the salespeople and were addressed.

Once this foundation was reset, the team began to reintegrate more indirect signals: the appointment of an e-commerce director, a change in the technology stack, or other events concerning an account.

This information can gradually enrich the scoring. At the time of the interview, however, Yves describes more of a system of priorities and SLAs than a complex automated score.

Why does iAdvize favor one-to-one over marketing automation?

Once a signal is identified, iAdvize favors individual contact. In the context of iAdvize, Yves Le Grouyer prefers a relationship developed through email, LinkedIn, and phone over overly generic email marketing campaigns.

Marketing provides the content and signals. The sales teams then maintain control over the contact process.

For BDRs, this prospecting mainly involves lemlist. At the time of the interview, iAdvize had been using the platform for about a year, for both email cadences and calling.

Yves also utilizes the data produced by these interactions. The day before the interview, for example, he had analyzed the BDRs' calls to understand which pitches worked, which worked less well, and how the results varied from one campaign to another.

The loop thus closes: signals trigger sales actions, and the resulting conversations allow marketing to better understand what works.

How does iAdvize use RB2B in the United States?

Website visitors also constitute a source of signals.

In the United States, iAdvize uses RB2B to identify certain visitors at the individual level. Yves specifies that this usage is limited to the United States due to the regulatory context. At the time of the interview, RB2B had only been deployed for about three months. Yves therefore prefers not to draw conclusions too quickly.

The tool makes it possible to reveal visits that would otherwise have remained anonymous. Some are interesting, others more difficult to interpret, especially when they come from paid search.

Summary of the software this article mentions in iAdvize's stack

StatusWorkflowToolUsage
In useGTM / data orchestrationCargoOrchestration of sources and signals
In useWeb intelligenceSimilarwebTraffic data
In useTechnographicsBuiltWithTechnological data
In useDataApifySource orchestrated via Cargo
In useOpen dataData.gouvFrench databases
In useEnrichmentFullEnrichEmail and phone
In useCRMSalesforceSource of truth and signal activation
In useMarketing automationHubSpotDestination of some orchestrated data
In useSocial network / intentLinkedInEngagement and prospecting
In useSales engagementlemlistEmail, calling, and interaction exploitation
In useConversation intelligenceModjoCalls and video calls, more with AEs
In useVisitor identificationRB2BIdentification of certain visitors

See iAdvize full stack →

Sign up to keep reading

It's free, and gives you access to the rest of this use case and every other article we publish.

Sign up

Already on Soft Atlas? Log in