Campaign
Choose the workflow and market context.
THE AUTOMATION PROBLEM
Gold price maintenance should not mean editing the same WordPress pages by hand all day.
A recurring gold-price workflow has several moving parts: retrieve current data, decide whether the job is a price refresh or a publishing task, execute it on schedule, avoid duplicate work, and record the result. GMIP brings those pieces into one campaign system instead of leaving them as unrelated manual steps.
Schedule
Run manually or according to a recurring schedule.
Price Source
Retrieve data through configured API-source roles.
Queue
Operational tasks enter the campaign execution flow.
Refresh / Publish
Update price data or run the selected content workflow.
Protect
Apply recurring-work safeguards and duplicate protection.
Log
Record the run result, timing and execution details.
PRICE UPDATES ONLY
WITHOUT SEPARATION
WITH GMIP
A changing gold price does not have to create a new article every time.
GMIP separates price maintenance from editorial publishing. In the Campaign Builder, Price Updates Only appears alongside Daily National Report, City Content and Weekly Report as its own workflow.
Price change → new post?
- Unnecessary publishing can accumulate.
- Price maintenance becomes mixed with editorial output.
- Recurring work is harder to control.
Price refresh can stay a price refresh.
- Use Price Updates Only when the job is maintenance.
- Use report modes when the job is publishing.
- Keep each campaign aligned with its actual purpose.
CAMPAIGN SCHEDULING
Control when the price workflow runs instead of relying on manual reminders.
The GMIP campaign architecture supports manual and recurring scheduling. The current campaign interface also provides a visible example of an active automatic price refresh configured every 3 hours.
Run on demand
Useful for testing, controlled operations or workflows that should not run automatically.
Every few hours
Use interval-based execution for recurring price or publishing jobs.
Daily workflow
Appropriate for recurring national reporting and scheduled market operations.
Weekly workflow
Keep weekly reporting separate from more frequent price refresh activity.
CRON, QUEUE & SYSTEM HEALTH
Automation should have an operational surface inside WordPress.
The GMIP Command Center exposes the parts that matter when recurring work is running: price-source readiness, WP-Cron status, publishing-queue health, pending tasks, image-library availability and campaigns that need review.
- WP-Cron status visible from the Command Center
- Publishing Queue health status
- Pending task count
- Price-source readiness
- Campaign review state
- Quick access to Data Center, Schema Check and market pages
Why this matters
An automated task is easier to trust when the publisher can see whether the scheduler, queue and data sources are healthy instead of discovering problems only after content becomes stale.
CAMPAIGN EXECUTION MODEL
Break recurring work into traceable campaign tasks instead of one oversized cron request.
The documented GMIP campaign architecture is designed so a due campaign can be divided into smaller jobs such as market-price retrieval, national content, city work, weekly reporting and run finalization. That makes the operation easier to track and retry than a single opaque process.
Fetch & update market price
Retrieve the market data required by the campaign and update its price context.
National workflow
Create or update the national-report task when that content mode is enabled.
Selected city tasks
Process selected cities as individual campaign work rather than one unbounded block.
Finish & record
Complete the run and update the campaign's run status and operational statistics.
CAMPAIGN RUN LOG
See what ran, what happened and how long it took.
GMIP gives recurring automation a traceable run history. The current Run Log shows the campaign, country, source, result, posts, cities, start time, duration and execution details for the latest runs.
CampaignWhich workflow ran
ResultSuccessful or failed state
PostsPublishing activity
CitiesCity-task count
DurationExecution timing
Duplicate Protection
The current Run Log screen explicitly shows Duplicate Protection Enabled and explains that when saved campaigns exist, the legacy automatic publisher stops to prevent duplicate posts outside the campaign system.
PRICE-SOURCE RESILIENCE
Go deeper into GMIP live-price data management →
Scheduled automation is only as useful as the price-data layer behind it.
The current Price API Management interface separates source roles into Primary, Secondary and Emergency Backup keys, with a separate Visitor Live Ticker key. It also reports source health through connection state, successful calls, failures, consecutive failures and latency.
PRIMARYMain price providerPrimary configured connection.
BACKUPSecondary sourceFirst backup role.
EMERGENCYEmergency backupAdditional fallback source role.
VISITORLive ticker keySeparate visitor-facing live-update access.
WHEN AUTOMATIC PRICE UPDATES MATTER
Use automation differently depending on what the website actually publishes.
Keep existing market information refreshed
Use Price Updates Only when the primary need is maintaining current price information without publishing a new story.
Separate updates from editorial reports
Run price maintenance independently from Daily National Report, City Content or Weekly Report workflows.
GMIP for news websites →Support localized market coverage
Keep price and publishing workflows connected to selected city coverage inside the campaign model.
Explore market & country operations →Extend automation beyond the price itself
Use campaigns to connect data, content type, cities, scheduling and SEO into a larger publishing workflow.
Explore content automation →FAQ
Automatic Gold Price Updates for WordPress — common questions
Can GMIP automatically update gold prices in WordPress?
Yes. GMIP uses campaign-based scheduling and includes a Price Updates Only workflow for recurring price maintenance.
Does every gold price update publish a new article?
No. Price Updates Only is a separate campaign content mode, so price maintenance can be kept separate from Daily National Report, City Content and Weekly Report workflows.
Can I schedule recurring updates?
Yes. The campaign architecture supports recurring scheduling, and the current Manage Publishing Campaigns interface visibly shows an automatic price-refresh example configured every 3 hours.
Can I see whether an automated run succeeded?
Yes. The Campaign Run Log records the campaign, country, source, result, posts, city tasks, start time, duration and execution details.
Does GMIP protect against duplicate automatic publishing?
The current Run Log interface explicitly displays Duplicate Protection Enabled for the campaign-based publishing workflow.
What happens if a price source has a problem?
The current API management interface supports primary, secondary and emergency backup source roles and exposes API health metrics. The campaign architecture is designed so source failures can be observed and recurring operations can be handled through controlled runs rather than an invisible one-off script.
Where can I compare GMIP plans and current prices?
Use the main GMIP pricing section. This feature page focuses on automatic price-update behavior and deliberately avoids duplicating the full pricing table.
GMIP AUTOMATION FOR WORDPRESS
Stop treating recurring gold-price maintenance as a manual editing task.
Explore the complete GMIP platform and choose the website and market scope that fits your gold-market operation.