Pharma & Compliance 101
We QA because of these reasons (multiple answers)
To remain compliant, avoid FDA fines, ensure a successful launch, avoid mistakes, etc.
All paid search launch QAs (launch, YouTube, re-review, post-launch, test plan, etc.) must be completed using this
Smartsheet
This is why we fill out the FUSE to Engine Audit
Make sure what is in the engine is approved in FUSE
We have quarterly QA days because of this reason
To remain compliant, share QA updates, etc.
We do this immediately if we see a compliance issue
Alert/ping/call your manager
We complete this 3 days after launching/going live with new campaigns
Test plan
This is what we copy into the orange section of the FUSE to Engine Audit
Approved submission content (found in FUSE)
This is the naming convention of the asset launch folder
JOB CODES BRAND AUDIENCE CAMPAIGN TYPE PAID SEARCH (ex: FA-1234567-FA-1234568 Scemblix DTC Branded Paid Search)
This type of asset (branded or unbranded) must NOT mention the indication the medication treats
Branded
We put the job codes (FA-12345678) in this part of the campaign name (different than our prior process)
After the funnel name/before benchmarking
This is what we do when we find something in the engine that is NOT approved in FUSE
Remove unapproved item(s) from bulksheet/engine & re-do that F2E Audit tab
This step is required for any new launches for supart H drugs
2253 submission
We use these as our ongoing compliance checks (multiple answers)
Daily health check, asset expiry tracker, SA360 rules, calendar reminders for expiration dates, etc.
We do this to the old campaigns when launching new campaigns
Add DNU, pause ad groups/keywords/ads, and set daily budget to $1
This is what we do if we are intentionally leaving out an asset that was approved OR the URL is correct but isn't matching (ex: doesn't have https:// in front)
Leave a note & duplicate the tab to show it is matching
When uploading sitelinks during a refresh, we do this in the editor
add (+), not make multiple changes