WEBAKTIVA / HELP CENTER Learn. Connect. Your practical module-by-module guide, from first login to automation, advertising and reporting.
Documented version 0.21 · Reviewed 2026-10-26 · 23 chapters
Open workspace ↗ 01 / WEBAKTIVA Website marketing and content Create a named content draft in Website marketing using the current editor fields. Define message, destination and objective, then save and preview before requesting website use. Register the exact HTTPS origin in Website installation and publish a reviewed draft snapshot. Inline content requires a #id or .class target. Install the SDK and connect your CMP: setConsent(true) only after marketing consent, setConsent(false) on withdrawal. It starts disabled and displays published content by path prefix. Frequency uses consented per-session storage. The SDK renders plain text and anonymous events without identifying contacts. Advanced recommendations, push and A/B remain pending. Back to contents ↑ 02 / WEBAKTIVA Getting started Sign in at /login/. An administrator must assign at least one company; an account does not automatically connect your channels. Check the selected company before importing data or preparing an action. Contacts, credentials and content belong to that company. Complete Brand and context with your business, audience, tone and restrictions. Start with a draft and your own test audience. Review Connections and Development. A visible module may still require credentials, permissions or installation. Recommended path: brand → contacts → draft → review → test → schedule → report. Back to contents ↑ 03 / WEBAKTIVA Access, passwords and security Choose Forgot password and enter your account email. The generic response protects account identities. The worker prepares the recovery email. Check spam and allow a few minutes; delivery depends on configured SMTP. Open the link and choose a password of at least 12 characters and at most 72 bytes. The link expires after 30 minutes and works once. Changing the password invalidates old reset links and sessions. Sign in again and keep private links and event keys secret. Request another link if it expired. Never send passwords or verification codes to support. Back to contents ↑ 04 / WEBAKTIVA Contacts, import and consent Open Contacts and review the form/import fields and statuses before uploading CSV. Keep an original backup outside the platform. Use valid emails, names and consistent tags. Import a few rows first and inspect the results before the full file. A contact is not automatically a subscriber: purchases and imported orders do not grant marketing consent. Keep evidence and source of consent. Check status after importing and before campaigns. Respect unsubscribes and bounce exclusions; never automatically resubscribe them. Having more contacts than subscribers is normal. Sendable audiences depend on status and exclusions. Back to contents ↑ 05 / WEBAKTIVA Dynamic segments Create a named draft in Segments, such as Summer prospects. Choose supported fields, operators and values. Decide whether all or any rules must match and check tags and spacing. Save and inspect matching contacts. Empty segments may be valid; verify source data before broadening rules. Use the segment for campaigns or entry triggers. Data changes and the worker can change membership. Current segmentation does not include every advanced condition planned for future releases. Back to contents ↑ 06 / WEBAKTIVA Create and review emails Create content in Email marketing using the current title, subject and body fields. Save before previewing. Review HTTPS links, spelling, sender and audience fit. Avoid scripts and email-client-incompatible styling. Give AI an objective and context; verify facts, prices and claims. The result is a draft, not a delivery. Use available test options with your own address. Inspect the received message before selecting the content in Campaigns. The current editor and previews do not imply every roadmap visual editor, A/B or heatmap feature is implemented. Back to contents ↑ 07 / WEBAKTIVA List campaigns and scheduling Select the email and subscriber/segment audience in Campaigns. Review expected counts and exclusions. Check SMTP, sender and limits in Administration. Platform quotas do not replace provider limits. Check each screen’s displayed date and timezone; Executions uses UTC. Confirm scheduling only after reviewing content and destination. Inspect queue states and errors after the worker runs. Pending, SMTP acceptance and inbox delivery are different outcomes. Real sends require owner review and authorization. Investigate ambiguous results before retrying to avoid duplicates. Back to contents ↑ 08 / WEBAKTIVA Unsubscribes and bounces Campaign messages include a signed unsubscribe link. Check it during testing and respect subsequent exclusions. Use the configured mechanism in Email bounces: DSN, signed webhook or POP3 mailbox over TLS. Providers require their own setup. Configure an authorized notification mailbox in Administration. Review scope before using a general personal mailbox. Inspect errors, duplicates and exclusions. Permanent bounces suppress sends; temporary failures need interpretation. Automatic reception requires an authorized mailbox or webhook, even when the module is published. Back to contents ↑ 09 / WEBAKTIVA Journeys, branches and waits Create a journey with a start, actions and an end. Begin with a small example before adding branches. Use supported fields and operators for conditions. Review both branch targets; 0 means end. Set waits in minutes and choose content IDs from the same company. Prepare email creates a proposal; Send email enters the real SMTP queue. Save and test with your own contact. Inspect the frozen version and steps in Executions and content in the review inbox. Editing a draft does not rewrite a frozen execution. Cart journeys require an integration emitting that event; installing the plugin alone does not supply it. Back to contents ↑ 10 / WEBAKTIVA Triggers and worker Choose the event or segment-entry trigger and the journey to start. Set supported reentry rules to prevent unwanted repeated actions for the same contact. Check worker heartbeat and errors. Hosting runs it every minute, but queues run in batches and waits are not exact-second guarantees. Troubleshoot in order: received event, company, rules, journey, due date, heartbeat and integration errors. Do not duplicate the hosting cron to accelerate tasks. Locks and idempotency help prevent duplicate processing. Back to contents ↑ 11 / WEBAKTIVA Connect social accounts and publish Start the configured network OAuth in Social publishing and select the correct identity. Review provider permissions. Distinguish profiles, pages and professional accounts. Instagram needs a compatible account and permissions; a personal Facebook session alone is insufficient. Prepare text and media, choose destinations and review content for each network. Formats and permissions differ. Schedule or confirm using the module options. Inspect remote states and links; an uploaded video may still be processing. Published code does not grant provider permissions. Renew or revoke access through the appropriate account; never reuse another company’s tokens. Back to contents ↑ 12 / WEBAKTIVA Images, videos, carousels and stories Upload supported JPEG, PNG or MP4 files in Media library. Check size, quota and preview before attaching. Order carousel images. Instagram uses containers; Facebook, LinkedIn and X have multi-photo flows depending on format and permissions. Wait for video processing. LinkedIn and X use multipart uploads; do not repeat an uncertain submission. Instagram Business and Facebook stories use different flows. Do not assume regular-post text and format support. Signed media URLs expire. Do not use them as permanent campaign or public-page links. Back to contents ↑ 13 / WEBAKTIVA Followers, metrics and external posts Authorize analytics access before requesting reports. Publishing access does not guarantee all metrics. Select a post or account in Social analytics and inspect sync time and state. Import external posts from an authorized identity in Accounts and posts. Reading is paginated and deduplicated without downloading media. Compare equivalent periods and export CSV when available. Missing data or permission errors do not mean zero followers or interactions. Social snapshots are retained for 90 days. History before connection is not fabricated. Back to contents ↑ 14 / WEBAKTIVA WooCommerce and PrestaShop Download the right ZIP from Connections and install on a staging copy first. WooCommerce requires PHP8.1+; PrestaShop targets8/9 and needs installation validation. Copy the company’s private event key to the store server. Select a specific PrestaShop shop and configure its private HTTPS cron. Queue the initial catalog. Pages contain separate variant IDs, native price, availability, stock and existing metadata. New orders sync without subscribing buyers. WooCommerce0.6.0 and PrestaShop0.6.0 offer optional daily reconciliation in their store settings. It starts disabled, preserves active traversals and uses WP-Cron for WooCommerce or the private cron for PrestaShop. Disconnect blocks new sends. Version0.7 modules archive native product retirements internally without deleting Google products. Carts use the private server API and are not captured by plugins. Catalog edits can shift paginated results; missing items are not inferred as deleted. They do not publish to Google. Back to contents ↑ 15 / WEBAKTIVA Merchant Center and diagnostics Authorize Merchant with the owning Google identity and choose the right account ID. Check domain and registration before interpreting errors. Connect in diagnostics-only mode first. Run a scan and inspect state, pages and issues; export CSV for review. New accounts may return zero products even if Google discovered website pages. Do not import products merely to force diagnostics. Separate write-enabled connections require an API source and explicit batch/removal review. Read-only connections block those actions. Read-only connections do not publish or modify products. Google issues may lag behind a correction; query again without hiding them. Back to contents ↑ 16 / WEBAKTIVA Google Ads, Meta Ads and budgets Connect the right account with provider OAuth in Ads and Shopping. Check currency and identity before drafting. Prepare Google Search or Meta with ad sets, targeting and creative. Remote structures start paused; AI proposals do not activate spend. Validate and review ad, destination, targeting, duration and budget cap. Activation requires owner review and an expiring single-use approval. Inspect Ads performance, costs and remote state. Request pause when needed and verify completion; a request alone is not an effective pause. Ad spend and platform cost are separate. Current flows cap1–1000EUR; Google Search requires3–7days and Meta1hour–7days. Investment is not increased automatically. Back to contents ↑ 17 / WEBAKTIVA Meta Conversions API Get a CAPI token and your company pixel/dataset ID from Meta. Configure HTTPS origin and begin with a required Test Events code. Production needs additional confirmation. Your server must send a paid order with meta_capi: advertising_consent boolean true, consent reference, stable event_id, recent UNIX event_time, query-free source_url and real user_agent. Plugins do not automatically supply this metadata. Open Review and check destination, mode and payload. The normalized SHA-256 email, User-Agent and reviewed purchase data are shared; a hash remains personal data. Approval expires after10min and config changes invalidate it. The worker sends approved events only. accepted means Meta reception, not attribution. Uncertain outcomes are not retried. Disconnect cancels pending jobs; changed purchase data or consent withdrawal block sending. Real validation needs an authorized dataset. Tests sent no real events. Use the same event_id for Pixel and CAPI deduplication. Events must be less than7days old; local retention90days. Back to contents ↑ 18 / WEBAKTIVA Conversions and optimization rules Configure the WEBPAGE conversion and verified send_to. Tracking code requires installation and explicit consent before collecting events. Check transaction IDs for deduplication. An imported order does not prove the browser sent an Ads conversion. Define no-conversion cost, high CPA or low ROAS rules with minimum samples and sufficient evidence. Begin with suggestions. Automatic pause requires authorization and limits; review data and attribution windows first. Advanced Shopping remains pending. Meta CAPI supports private-server purchase events with dedicated credentials, explicit consent and owner review. They are distinct from published Search flows and internal order ingestion. Back to contents ↑ 19 / WEBAKTIVA Core Web Vitals, history and alerts Create a Core Web Vitals monitor with URL/origin and mobile/desktop device. Each combination uses one monitor slot. Configure restricted CrUX and PageSpeed keys in Administration. PageSpeed lab data and CrUX field data are different sources. Run an initial measurement and inspect date, source, state and notes. No CrUX samples means insufficient public data, not a zero score. Inspect LCP, INP and CLS, compare history and export CSV. Current alerts appear in the panel; email alerts are not implied. Good thresholds: LCP≤2500ms, INP≤200ms, CLS≤0.1. History is retained up to365days; external quotas still apply. Back to contents ↑ 20 / WEBAKTIVA Google Analytics and Search Console Configure OAuth and authorize read access from Connections using an identity with property access. Enter the numeric GA4 property ID and exact Search Console URL property or sc-domain:domain. The measurement ID is not the property ID. Save and request sync. Resolve property or permission errors before assuming traffic is absent. The worker reads authorized properties every six hours. Check data freshness and provider reporting windows when comparing reports. Merchant OAuth is separate. Connecting Merchant does not authorize Analytics or Search Console. Back to contents ↑ 21 / WEBAKTIVA AI assistant, credits and review Store the OpenAI key in Administration, never public JavaScript or brand context. Real generation requires a key. Complete Brand and context, then choose copy, email, social, journey, segment or analysis in AI assistant. Review credit cost before confirmation. Context and prompts are sent to OpenAI. Minimize personal data and never include passwords, tokens or information you cannot share. Review response and history for facts, tone, links and claims. Copying or saving output does not publish or send it. Copy/social cost1credit, email3, journey/segment/analysis5; Ads proposals5. Review reservations and uncertain responses before retrying; no automatic top-ups. Back to contents ↑ 22 / WEBAKTIVA Events API and custom integration Get the private key from Connections in the correct company. Store it only in your service or store backend. Send events with a unique event_key, type and data to the displayed endpoint. Reuse the event key when retrying the same occurrence. For products/orders use the displayed Connections format with up to100records per request. Keep external_id stable and currency/status correct. Validate with authorized test examples first. Inspect HTTP responses, validation errors, company isolation and purchase events before enabling automation. Receiving an event does not install visitor tracking or automatically collect consent. Integrations must send only real, authorized events. Back to contents ↑ 23 / WEBAKTIVA Reports, troubleshooting and routine Daily, inspect heartbeat, failed queues, expired permissions and scheduled posts. Separate pending tasks from uncertain outcomes. Weekly, review bounces, unsubscribes, AI use, performance and report freshness. Export only data you are authorized to process. Record module, company, time, state and error message without passwords or tokens. Do not repeat campaigns or payments as a test. Check Availability, this tutorial and the changelog before assuming roadmap features exist. Contact info@interaktiva.es with minimal relevant context. This manual describes the published version. Real-account integration validation remains separate from code tests. Back to contents ↑ Changelog and documentation updates 0.21 · Meta CAPI: explicit consent, review and conversion queue. 0.20 · Website installation and consented SDK; private-API carts and reversible internal retirement. 0.19 · PrestaShop: optional daily reconciliation with preserved progress. 0.18.2 · Online help center with search and contents. 0.18.1 · WooCommerce0.6.0: optional daily catalog reconciliation. 0.18 · PrestaShop combinations, WooCommerce stock and password recovery. 0.17 · Variant metadata and diagnostics Merchant connection. This manual is built and published with the website. The build checks functional source files and blocks publication after changes until the tutorial is reviewed. The date marks an actual review; AI does not automatically rewrite this content.
Check feature availability ↗ 