Nexus Marketing
Nexus Marketing takes your website’s marketing data to Nexus. With a single component you work with three things: content resources (blog posts, news, case studies, guides and landing pages) with their daily metrics, your website’s daily analytics, and SEO and GEO audits.
It is useful to connect your content management system or your analytics tool with Nexus: every time you publish an article, or every night with the previous day’s data.
When to use it
- Every time you publish an article on your blog, you want to add it to Nexus as a resource.
- Every night you want to send Nexus the previous day’s website visits, in total or by channel and campaign.
- You want to send each article’s views, reading time and conversions.
- A tool audits your website’s SEO and you want to keep its score in Nexus.
Configuration
You need a Nexus credential with your Nexus address (for example https://nexus.your-company.com) and an application key that starts with nxa_live_. See Credentials.
A Nexus administrator creates the key in Administration › Integrations › API keys, with New API key. Choose NappAI CMS website in What it is for: it includes the Content, Visits and SEO/GEO permissions this component needs. When it is created, Nexus shows the API key and the Nexus address: they are the two pieces of the credential.
| Field | What it does |
|---|---|
| Credential (required) | The Nexus credential. It fills in Nexus address and Nexus API key for you. |
| Resource | What you work with: Resources (content resources), Web (web analytics) or SEO (audits). Default: Resources. |
| Operation | What you do. The list changes with the chosen Resource. See Resources and operations. |
| Idempotency key (advanced) | Optional. If you repeat the same key within 24 hours, Nexus doesn’t do the write again. It keeps a retry from repeating the same thing. |
Resources and operations
Resources (content resources)
| Operation | What it does | Fields |
|---|---|---|
Upsert Resource | Creates a resource or, if one already exists with that External ID, updates it. | External ID, Type, Title, URL. Optional: Summary, Thumbnail URL, Language, Published at, Category and Tags. |
Archive Resource | Archives a resource. | External ID |
Resource Metrics | Sends a resource’s daily metrics. | External ID, Date, and Views, Visitors, Average time (s) and Conversions; or several days in Several days (JSON). |
- External ID is your ID for the content, for example the article’s slug. It can’t repeat with the same key.
- Type can be
BLOG_POST,NEWS,CASE_STUDY,GUIDEorLANDING_PAGE. - Summary takes up to 4,000 characters. Language is a code such as
esoren-US. Published at is a date and time, for example2026-11-09T09:00:00Z. - Category is created in Nexus if it doesn’t exist. Tags are labels separated by commas, up to 20.
Upsert Resourcealso reactivates an archived resource. Only creating it fires theresource.createdevent.- Date is the day of the metrics, such as
2026-11-08, ortoday. Visitors and Conversions can’t be more than Views. If you send the same day again, it replaces the previous one. - Several days (JSON) replaces the single day: a list such as
[{"date": "2026-10-12", "views": 340, "visitors": 280}], up to 100 days.
Web (web analytics)
| Operation | What it does | Fields |
|---|---|---|
Web Metrics | Sends one day of your website’s analytics, in total or by channel and campaign. | Site, Date, Visitors, Page views. Optional: Entries, Bounces, Conversions, Source, Medium and Campaign; or several rows in Several rows (JSON). |
- Site is the website’s domain, for example
nappai.es. If you type a full address, only the domain is sent. - Page views can’t be fewer than Visitors, and Entries (sessions started) and Bounces can’t be more than Visitors. Conversions can’t be more than Page views.
- Source (for example
google), Medium (cpc,organic…) and Campaign split the data by channel. If you leave all three empty, the row is the day’s total. - Several rows (JSON) replaces the single row: a list such as
[{"site": "nappai.es", "date": "2026-10-12", "visitors": 950, "pageviews": 2400}], up to 100 rows.
SEO (SEO and GEO audits)
| Operation | What it does | Fields |
|---|---|---|
SEO Audit | Saves an audit of your website with its scores, its pages and its findings. | Site, Score. Optional: Audited at, SEO score, GEO score, Tool, Pages (JSON) and Findings (JSON). |
- Score, SEO score and GEO score go from 0 to 100. GEO score measures visibility in AI search engines.
- Audited at is the audit’s date and time. If you leave it empty, the current moment is used.
- Tool is the name of the tool that audited, up to 80 characters. If you leave it empty,
nappaiis sent. - Pages (JSON) is each page’s score, for example
[{"url": "/pricing", "score": 74, "geo_score": 60}], up to 500 pages. - Findings (JSON) is the number of findings by severity, for example
{"critical": 1, "warning": 6, "info": 12}. - Two audits of the same site at the same moment are merged into one.
Amounts are sent as whole numbers, rounded: 12.7 is sent as 13. Thousands separators are understood in both styles (1.500 and 1,500 are 1500).
Output
The Data output returns Nexus’s answer: the resource created or updated, or the confirmation of the metrics and the audit received.
The component supports Batch Mode and it can be connected to an Agent as a tool. See Tools.
Example
An agency wants every new article on its blog to appear in Nexus.
- The content management system notifies the flow through a Webhook Input every time it publishes an article, with its slug, its title, its address and its summary.
- Add Nexus Marketing with the
Resourcesresource and theUpsert Resourceoperation. - In External ID put the slug, in Type
BLOG_POST, and in Title, URL and Summary the article’s details. - If the article is edited, the same flow updates it in Nexus, because the External ID is the same.
For analytics, create another flow in the Scheduler that every night reads the previous day’s visits and sends them with Web Metrics.
Good practices
- Always use the same External ID for the same content: this way it is updated instead of duplicated.
- If you send the metrics of a day that hasn’t finished yet, send them again the next day: the last write for each day replaces the previous one.
Security and limitations
- Nexus rejects metrics with a future date.
- Only the domain is kept in Site: the path and the
https://are removed. - The Nexus key can only send data: it can’t read the CRM.
- If Nexus rejects the key, it may be revoked, paused or missing the permission needed. An administrator can check it in Administration › Integrations.
- Nexus limits the number of writes per minute. If you go over it, the component tells you how many seconds to wait.
Related components
- Nexus Intake: send leads and their activity.
- Nexus Webhook: starts the flow with what happens in Nexus, also when a resource is created.