Can we store protected health information in Strkr for a patient-journey marketing use case?
No. Strkr is not HIPAA-certified for storing protected health information and does not sign a Business Associate Agreement that covers CRM or marketing contents as a PHI data store. The product is designed for marketing to clinical professionals (nurses, pharmacists, department chairs, directors of service lines, administrators), not to patients. Clinical-professional contact records, campaign engagement history, consent timelines, meeting history, pricing scenarios, and the attribution model are the shape of the Strkr content. Patient identifiers, diagnosis codes, chart excerpts, and any other PHI must stay in an EHR or a HIPAA-certified system of record. If the marketing use case requires PHI in the platform (patient-journey marketing from inside a provider org, for example), Strkr is not the right fit, and the honest answer up front saves the sales cycle for both sides.
How does Strkr keep an ad pixel from leaking PII to Meta or Google?
Every Strkr form carries a pixel-safe toggle that strips email, phone, name, condition keywords, and known PHI parameters from outbound pixel payloads at submit time. The admin audit shows every pixel call per form with the full parameter list, the timestamp, and the destination network. A monthly pixel audit filter runs in 10 minutes and confirms no PII leaked to Meta, Google, or LinkedIn. The conversion still fires. The payload is clean. The ad account stays safe, the privacy officer gets a clean answer, and the marketing team keeps shipping without a legal pre-flight on every form. Admin controls at the tenant level enforce the pixel-safe default so a careless form configuration cannot override the posture.
How does Strkr handle multi-touch attribution across a 14-month sales cycle?
Strkr attribution runs across the full lifecycle timeline with configurable models (first-touch, last-touch, linear, time-decay, u-shape, w-shape) and ships the formula engine that computes the credit split on the Opp record. Every campaign touch (ad click, form fill, webinar attendance, content download, email open, demo booking) lands on the contact timeline with campaign metadata preserved. When the Opp closes 14 months later, the attribution model reads the full touch history for every contact on the deal and splits the credit by the configured model. The quarterly budget review ties pipeline back to the campaign that actually produced it, and the long-cycle credit shows up on the right side of the campaign dashboard with the touch-timing distribution.
Does Strkr replace Marketo (or HubSpot, or Pardot) plus Salesforce Health Cloud for a healthcare marketing team?
For most healthcare SaaS, medical device, and services vendor marketing teams running professional-audience demand gen, yes. Strkr covers clinical audience segmentation, pixel-safe forms, nurture flows with consent gating, legal-approved asset approval, campaign ROI reporting, multi-touch attribution across the 9 to 18 month cycle, MQL to SQL to Opp to Closed lifecycle on one timeline, and the CRM the sales team runs on the same platform. For teams whose marketing itself touches PHI (patient-journey marketing from a provider org, for example), a HIPAA-certified platform is the right place for the patient-facing layer, and Strkr handles the professional-audience motion alongside it. Strkr ships native migration paths that preserve contacts, custom fields, campaign history, and attribution timelines from Marketo, HubSpot, Pardot, and Salesforce.
How does Strkr handle the asset approval cycle so legal review does not slip ship dates?
Every landing page, email, ad, and gated asset runs through Strkr asset approval with four stages: draft, review, legal sign-off, approved. The approved version locks and carries a signed timestamp from the legal reviewer. A new edit creates a new draft that has to re-clear review before send. The marketing team cannot accidentally ship an unapproved edit because the send flow checks approval status at send time and blocks a non-approved asset. The compliance officer audit in Q4 lands on an approval trail per asset instead of a Google Doc history dig, and the legal reviewer sees a dashboard of pending approvals with age so nothing sits in review for three weeks because somebody forgot to ping them on Slack.
How does Strkr handle consent for a nurture send to clinicians at hospital addresses?
Strkr tracks every consent event per contact (source, timestamp, campaign, IP, consent text version) and renders a consent timeline on the contact record. Every nurture email fires through a consent-check that reads the contact consent timeline, confirms current opt-in for the specific channel and purpose, and skips the send if consent lapsed or was never granted. The admin sees a per-nurture skip report with the specific consent reason so the segmentation can be tightened for the next run. If a privacy officer complaint lands, the audit answer is a filter on the consent timeline that returns the opt-in event with the full context. The unsubscribe flow preserves the full history instead of flipping a boolean the audit cannot reconstruct, and the preference center lets the contact adjust channel and purpose granularity without a full unsubscribe when the contact wants to stay opted into a different stream.
