Connectif enabled custom-integration and custom-event-type endpoints in its public API July 8, 2026, according to the corresponding entry in its product changelog.
The release expands a specific marketing surface: connecting business events with communication journeys. Its value is not demonstrated by the number of connected systems. It depends on an event retaining its meaning, arriving in time and supporting a useful customer decision, alongside measurement that separates operational savings from additional commercial contribution to the business.
The provider's changelog also announces a workflow calendar and a statistical-summary view in the workflow list. CONNECTIF ARTIFICIAL INTELLIGENCE, S.L.U., identifies its address and commercial registration in Murcia in its legal notice . The sources document feature availability without publishing a customer-sales comparison establishing the release's commercial effect.
A connection begins with a business definition
A purchase, return and resolved query have different meanings. Exchanging a notification does not establish by itself which one occurred. Marketing and technology should agree the event name, its unit and when it becomes valid. This is a proposed deployment principle, not a description of a particular retailer's use of the features made available in the July release.
The distinction between creating an integration, defining an event type and sending an instance matters operationally. The definition describes expected information; the instance corresponds to a particular occurrence. Keeping those tasks separate would allow controlled definition changes and prevent a configuration update being mistaken for new customer activity. The business fact should remain identifiable independently of the work required to configure its representation.
More cloud software does not remove integration work
For technological-capacity context, Spain's INE reports that 44.3% of surveyed businesses with at least 10 employees used paid cloud services and 16.8% employed ICT specialists in first-quarter 2025 . The survey covers sectors specified in its methodology, with approximately 15,000 businesses in this size category and stratified sampling by size, activity and autonomous community.
These measure adoption and resources, rather than Connectif users or correct integrations. They cannot identify which firms lack integration capacity because the categories can overlap and their cross-tabulation is not supplied here. They do explain why an API release needs consideration of who can design, review and maintain communication between applications, alongside whether the applications themselves are commercially available.
Integrating data is a different challenge from defining the journey
Challenges reported by B2B marketing professionals, February 2025 reference. Three selected responses.
Tap or hover for details. All values are also available in the data table.
Collapse notes
Act-On/Ascend2 via Statista: 207 B2B professionals, reference as of February 12, 2025. Statista labels the scope worldwide; the original 2025 country list is not separately confirmed. Exact fieldwork dates, interview mode and weighting are unverified. The current publisher page concerns a different edition. Non-exclusive answers, not a sample of Connectif customers or all retailers.
Explore the data table
| Category | Professionals citing challenge |
|---|---|
| Quality data | 49% |
| Integrating technology and data | 42% |
| Effective buying journeys | 41% |
In the B2B survey reported by Statista, 42% cited integrating technology and data, while 41% cited building effective journeys. These are reported difficulties rather than audited failures. Their proximity illustrates two tasks the new API does not combine by itself: carrying an event and deciding which conversation should change when it occurs.
Identity, time and state determine an event's usefulness
Relevant communication needs to recognise the correct relationship. An application's contact identifier may not correspond directly to another system's identifier. A proposed review would document how those identities relate and what happens when correspondence cannot be established. Guessing a match to complete a journey could affect someone else or produce communication without the context necessary for a useful commercial interaction.
The time of occurrence also deserves preservation. Receiving a notification today does not mean the purchase, query or preference change occurred today. If synchronisation resends earlier activity, using receipt time to trigger a message can treat a historical fact as a current need. The release documentation does not explain the rules of every deployment for resolving that difference.
Current state can contradict an accurate but old event. A purchase may have been cancelled or returned before an associated communication is processed. The proposed design should identify the source confirming the current situation when the distinction matters. Demonstrating error-free arrival of the original notification is insufficient if the resulting message uses customer context that is no longer commercially valid.
A technical repetition is not another customer decision
Systems can resend information when they need confirmation that an operation completed. Journey evaluation should distinguish the real business action from the number of received notifications. Two notifications for one order do not establish two purchases. Counting them as commercial activity can distort both automation and interpretation of its results, even if each individual transmission succeeds technically.
Recovery after an interruption presents another decision. Processing pending notifications may be appropriate for reconciling records but inappropriate for sending communications that have lost usefulness. The team needs to distinguish preserving business history from triggering a commercial action. Completing a delayed transfer does not automatically justify contacting a customer about every earlier event reproduced by the recovery process.
A calendar reveals concurrency rather than deciding priorities
The announced workflow calendar offers a view for examining when planned actions coincide. With several journeys, coincidence can have commercial consequences: one person could be eligible for communications serving different objectives. Seeing activity over time can support coordination without establishing that the tool automatically decides which business objective should take precedence for that particular customer.
Priority needs a business rule. A message resolving a service need and a promotion may require different treatment. The decision should not depend only on which application transmitted a notification first. Teams can define limits and exceptions appropriate to their journeys, but the source does not publish a brand's actual rules or establish that those decisions have already been made.
From a received event to a commercial outcome
Intermediate measures locate difficulties, but the primary objective should match the funded decision. A project intended to save transfer time needs observation of work actually avoided. A project intended to recover purchases needs assessment of commercial contribution against a defined comparison. One activity indicator cannot demonstrate both effects simultaneously simply because it rises after a connection becomes available.
Reported automation success has degrees
Marketing decision-makers’ assessment of their own strategies, February 2024.
Tap or hover for details. All values are also available in the data table.
Collapse notes
Ascend2: 387 decision-makers in a February 2024 online survey; Statista labels the scope worldwide. Recruitment and weighting are not detailed. Perceived success rather than audited return; a different sample from the 207 B2B professionals surveyed in 2025.
Explore the data table
| Category | Surveyed decision-makers |
|---|---|
| Somewhat successful | 69% |
| Very successful | 28% |
| Unsuccessful | 3% |
In Ascend2’s study reported by Statista, 69% called their automation somewhat successful and 28% very successful. The question does not separate savings, sales or margin using a common standard. For a Connectif event, that gap makes naming the outcome essential before calling it success: less manual reconciliation and more net purchases require different observations.
Causal measurement needs a question before the result
A proposed commercial evaluation could assign a comparable eligible group without a particular promotional message while maintaining necessary service. The comparison would include everyone assigned, including non-buyers. This is a way to assess additional contribution rather than an experiment announced by a customer in the release documentation. Feature availability cannot establish that an intervention has been evaluated under those conditions.
Governing events includes deciding what not to transport
An event can contain more information than a commercial action needs. Before connecting data, the team should explain which fields it uses and why. Recording detail without a specific decision increases maintenance and complicates review. The ability to transport a field does not establish that its use is helpful or appropriate across every communication journey a business might later choose to build.
The definition needs commercial and technical owners sharing its meaning. A form or process change can alter data without changing the event's name. Without an owner maintaining that agreement, messages may continue executing against an outdated interpretation. The release's availability announcement does not guarantee the future quality of definitions created by individual companies or resolve organisational disagreements about those definitions.
What could justify investment
A cost evaluation should include event design, connection, maintenance and incident handling alongside applicable licensing. Work does not end when the first notification arrives. Changes in originating applications can require further review to preserve meaning and timeliness. Return depends on the journey being funded rather than a supposed universal value attached to integrating more applications or collecting more customer signals.
The decisive question for a Spanish brand is which fact should change the customer conversation and how the value of that change can be assessed. The expanded integration surface allows that question to be explored. Commercial quality will depend on the definition, timeliness and measurement of the event the business chooses to connect, with costs and outcomes kept separate from technical activity alone.
In this article
Marian Vasile
Marian Vasile is a MarTech and growth professional. His work spans product marketing, SEO, paid advertising and deep online tracking, including behavioral analytics and attribution.