How does this features catalog differ from the marketing-automation-features-and-benefits or marketing-automation-features-benefits pages?
This page catalogs features in pure enumeration form: what the platform does, with enough detail to evaluate against a competing product. The marketing-automation-features-and-benefits page pairs each feature with its specific benefit, which helps a buyer connect capability to outcome but is slower to scan when you just want to compare feature sets. The marketing-automation-features-benefits page is outcome-first: it organizes around the benefits a team gets and uses features as evidence rather than as the primary structure. The three pages serve different evaluation moments: catalog for feature comparison, paired for first-time buyer orientation, outcome-first for executive narrative. Use the one that matches where you are in the evaluation.
What triggers and actions does the platform ship, and is 180-plus enough?
The 180-plus trigger and action count covers the real operational surface a marketing automation team needs. Trigger shapes: record-change (on create, update, delete, specific field change on any object), behavioral (page view, click, form submit, email event, chat conversation), time (cron, delay, specific time, recurring, time-zone-aware), deal/pipeline (deal created, stage advance, won, lost, amount threshold), inbound-event (webhook, email, API call). Action shapes: email (send campaign, send transactional, send cadence step, resend to non-openers), record (write field, tag, enroll, unenroll, update preference, apply score, create task), external (HTTP call to any REST API, native connector action, outbound webhook), logic (branch, loop, wait, approval gate). For logic that resists primitive expression, HTTP actions and code-block actions cover the long tail. For most mid-market B2B marketing teams, the primitive count covers common patterns and leaves room for extension through HTTP calls.
How does the segmentation engine stay fresh; is it batched or real time?
Strkr's segmentation engine runs on live CRM data. Segments define as filters on contact, account, deal, product-use, and custom fields. When any record field changes, the engine evaluates against every segment the record could belong to and updates membership in real time. There is no scheduled sync, no 15-minute stale window, no overnight batch. A contact that just upgraded to the enterprise segment reflects on the next automation evaluation. For teams running marketing automation alongside a separate CRM, segmentation freshness is a chronic pain point because the sync layer introduces delay. Strkr's one-platform posture (CRM and marketing automation on the same database) eliminates the sync layer entirely so freshness is a given rather than a feature.
What email deliverability tooling does the platform ship?
Deliverability tooling covers authentication, monitoring, and operational controls. Sender authentication: SPF, DKIM, and DMARC configure natively on sender domains, with the platform signing every outbound email. Multiple sender domains per tenant for brand or regional segmentation. Deliverability dashboard: reputation score per sender domain, bounce rate (hard and soft), complaint rate, and delivery distribution (inbox vs promotions tab vs spam) tracked over time with alerts on degradation. Suppression management: global suppression list for do-not-contact, hard bounces, repeated unsubscribes, plus per-campaign suppression. Preview and testing: email rendering preview across Gmail, Outlook, Apple Mail, mobile and desktop; spam-score checker; link checker. Volume throttling: configurable send rates per sender domain to protect reputation during large sends. For teams migrating from Mailchimp or SendGrid, Strkr's deliverability tooling matches or exceeds the feature set at comparable scale.
What consent management features does the platform ship for GDPR, CCPA, and CAN-SPAM compliance?
Consent management is native to the contact record rather than bolted on. Every outbound email checks consent before sending. Topic-level consent control lets recipients unsubscribe from product updates while remaining opted in to transactional notices and account notices separately, which supports the granular consent requirements of GDPR Article 7 and CAN-SPAM. Native unsubscribe links on every email with one-click unsubscribe that writes to the contact record immediately. Preference-center URLs let recipients manage consent per topic on a self-service surface. Every consent change; subscription opt-in, topic change, full unsubscribe, re-subscription; lands in the immutable audit log with the actor, timestamp, before-state, after-state, and source (email click, admin update, inbound form). The audit trail supports GDPR subject access requests and compliance reviews. For CCPA, the platform includes do-not-sell flag handling and subject right-to-delete flows that cascade to every related record. For HIPAA-regulated teams, the platform operates under BAA with the same consent primitives applied to protected health information.
What does the attribution reporting look like, and does it integrate with the CRM pipeline?
Attribution reports apply five models; first-touch, last-touch, linear, time-decay, and position-based; on the same event stream, so model switching produces precise comparisons without data-layer loss. Because Strkr runs CRM and marketing automation on one database, attribution reads from one event stream without the sync-layer fidelity drop that happens when attribution has to combine events across a dedicated marketing automation tool and a separate CRM. Marketing-sourced pipeline rolls up on the CRO forecast surface alongside sales-sourced. Marketing-influenced pipeline tracks separately (deals that touched a marketing journey at some point without being marketing-sourced). Per-campaign reports show not just open rate and click rate but opportunity-created rate and revenue attributed. Per-journey reports show enrollment volume, step-by-step conversion, average time to conversion, and revenue per enrolled contact. BI tool exports to Looker, Tableau, PowerBI, and Metabase let RevOps leads build custom attribution dashboards on top of native metrics. The attribution surface connects marketing activity to the revenue conversation precisely.
