™️ CIPO Trademarks Journal Change Watch

Seed-zero weekly change feed over the public, logged-out CIPO Trademarks Journal (Canadian Intellectual Property Office, published each Wednesday). It emits confirmed Journal events on the marks you watch — advertisements (advertised for opposition), registrations, extensions, amendments, section 9 public notices/withdrawals, and errata — as deltas, not a commodity application dump.

Output is one journal_record row per result; billing is pay-per-event, the value event being one confirmed journal event delta (a $0.02 start fee per run, then $0.08 per confirmed journal event delta). Source: www.ic.gc.ca.

Use with

Pair with your docketing system: schedule weekly, feed trademark_delta rows into your matter records keyed by composite_id (CIPO application/registration number).

📊 Sample Output

Real rows from run wTDw5ic2eLKPOlUJ0 on build 0.1.17 (2026-09-23), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

issue_date	event_type	section_heading	composite_id	composite_key	owner_name
2026-09-23	ADVERTISEMENT	ADVERTISEMENT	CIPO:APP1798628	2026-09-23|ADVERTISEMENT|APP:1798628	IMI PLC
2026-09-23	ADVERTISEMENT	ADVERTISEMENT	CIPO:APP1817816	2026-09-23|ADVERTISEMENT|APP:1817816	Spike Cable Networks Inc.
2026-09-23	ADVERTISEMENT	ADVERTISEMENT	CIPO:APP1919218	2026-09-23|ADVERTISEMENT|APP:1919218	Frank J. Zamboni & Co., Inc.
2026-09-23	ADVERTISEMENT	ADVERTISEMENT	CIPO:APP1949849	2026-09-23|ADVERTISEMENT|APP:1949849	Marolina Outdoor Inc.
2026-09-23	ADVERTISEMENT	ADVERTISEMENT	CIPO:APP1967452	2026-09-23|ADVERTISEMENT|APP:1967452	femmebought Community NFP
2026-09-23	ADVERTISEMENT	ADVERTISEMENT	CIPO:APP1967453	2026-09-23|ADVERTISEMENT|APP:1967453	femmebought Community NFP
2026-09-23	ADVERTISEMENT	ADVERTISEMENT	CIPO:APP1967454	2026-09-23|ADVERTISEMENT|APP:1967454	femmebought Community NFP
2026-09-23	ADVERTISEMENT	ADVERTISEMENT	CIPO:APP1967455	2026-09-23|ADVERTISEMENT|APP:1967455	femmebought Community NFP

The run finished with the status message: PARTIAL_MAX_ITEMS: capped at 10

✅ What you get

One of three record types discriminated by record_type: trademark_delta (watch signal), journal_record (snapshot), or source_receipt (never billed).

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_type (string) — e.g. journal_record
• office — e.g. CIPO
• issue_date — e.g. 2026-09-23
• issue_number — e.g. 39
• event_type — e.g. ADVERTISEMENT
• section_heading — e.g. ADVERTISEMENT
• application_number — e.g. 1798628
• registration_number — null in every sample row
• international_registration_number — null in every sample row
• composite_id — e.g. CIPO:APP1798628
• composite_key — e.g. 2026-09-23|ADVERTISEMENT|APP:1798628
• mark_text — null in every sample row
• owner_name — e.g. IMI PLC
• international_classes — e.g. [6, 7, 9, 11, 17, 20, 37, 42]
• goods_services — null in every sample row
• filing_date — e.g. 2016-09-01
• publication_date — e.g. 2026-09-23
• registration_date — null in every sample row
• source_url (string) — e.g. https://www.ic.gc.ca/opic-cipo/tmj/eng/view.html?year=2026&edition=09-23&file=Jo
• observed_at (string) — e.g. 2026-09-23T17:30:19Z
• source_hash — e.g. b80d3a634238081a7074c270c7096884e512ae0dfed027e6515afc7efc28ebed

What you get

• trademark_delta (primary): one row per newly-confirmed Journal event for a watched mark. Delta types mirror official section events; CORRECTED_ENTRY fires when a later Erratum changes a previously-printed entry.
• journal_record (snapshot mode only): the parsed records of one edition.
• source_receipt (never billed): per-issue and per-run provenance, canary, HTTP status, and terminal state — fail-loud, never a silent empty.

Composite identity is office-scoped: CIPO + application/registration number. Status deltas use official Journal section events; the actor never infers infringement or legal outcome.

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "watchMode": false,
  "maxItems": 10,
  "maxCatchupIssues": 1
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 0 × $0.08 trademark_delta + 1 × $0.10 journal_issue_check = $0.12 on the Free tier — snapshot preview rows are delivered unbilled; only the source check and the start fee were charged.

2. A smaller, narrowed run

{
  "watchMode": false,
  "maxItems": 5,
  "maxCatchupIssues": 1
}

Caps the run at 5 rows; same billing shape as the sample run above.

3. Watch mode on a schedule

{
  "watchMode": true,
  "maxItems": 10,
  "maxCatchupIssues": 1
}

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.08 each.

🧾 JSON sample record

One real record from run wTDw5ic2eLKPOlUJ0, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_type": "journal_record",
  "schema_version": "1.0",
  "office": "CIPO",
  "issue_date": "2026-09-23",
  "issue_number": 39,
  "event_type": "ADVERTISEMENT",
  "section_heading": "ADVERTISEMENT",
  "application_number": "1798628",
  "registration_number": null,
  "international_registration_number": null,
  "composite_id": "CIPO:APP1798628",
  "composite_key": "2026-09-23|ADVERTISEMENT|APP:1798628",
  "mark_text": null,
  "owner_name": "IMI PLC",
  "international_classes": [
    6,
    7,
    9,
    11,
    17,
    20,
    37,
    42
  ],
  "goods_services": null,
  "filing_date": "2016-09-01",
  "publication_date": "2026-09-23",
  "registration_date": null,
  "source_url": "https://www.ic.gc.ca/opic-cipo/tmj/eng/view.html?year=2026&edition=09-23&file=Journal_en.html",
  "observed_at": "2026-09-23T17:30:19Z",
  "source_hash": "b80d3a634238081a7074c270c7096884e512ae0dfed027e6515afc7efc28ebed"
}

🔧 How it works

Transport. Requests go through Apify residential proxy because the source refuses datacenter egress. robots.txt is read first and a disallowed path is never fetched.

Watch semantics. Snapshot mode (watch_mode: false) returns a preview. Watch mode keys every record on a source-native id, stores a private baseline in a named key-value store, and on each later run emits one delta row per change (new / changed / removed). A blocked fetch is never diffed, so a source outage cannot show up as a mass removal.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

Charging. Each confirmed journal event delta is charged at the moment it is pushed (trademark_delta); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

Who it is for

IP counsel and trademark docketing / compliance teams who must catch when a watched application is advertised for opposition, registered, amended, or corrected in the official Journal — without re-reading a 12 MB weekly issue by hand.

How the watch works

First run seeds the baseline and emits zero deltas. Later scheduled runs emit only events published since the last complete edition. Blocked or partial editions never advance the cursor and never fabricate removals — the Journal publishes events, not a current-status table, so absence is never a change.

Source & compliance

• Source: https://www.ic.gc.ca/opic-cipo/tmj/eng/home.html (public, logged-out, robots-allowed English HTML Journal editions).
• No login, no API key, no CAPTCHA solving, no paywall defeat. The CIPO search apps under /app/opic-cipo/... are robots-disallowed and are hard-blocked here.
• Public / logged-out / compliance-class. No predictive-performance claims.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console → Schedules → Create new, add this actor with input 3 above (watch_mode: true), and pick a cadence:

• Daily — 0 7 * * * (07:00 UTC): catch changes within a day.
• Weekly — 0 7 * * 1: a Monday digest.

Each run is independent; keep the same input on the schedule so the results stay comparable. Schedules can also POST results to a webhook (Console → Integrations).

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Confirmed Journal event delta (trademark_delta)	$0.08	$0.07	$0.06	$0.05
Journal edition processed (journal_issue_check)	$0.10	$0.09	$0.08	$0.07

Worked at the live Free-tier price (watch mode, one delta per change):

• 8 confirmed journal event deltas: $0.02 start + 8 × $0.08 = $0.66
• 25 confirmed journal event deltas: $0.02 start + 25 × $0.08 = $2.02
• 500 confirmed journal event deltas: $0.02 start + 500 × $0.08 = $40.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: PARTIAL_MAX_ITEMS: capped at 10. maxItems is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by www.ic.gc.ca. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (www.ic.gc.ca) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input (in watch mode the first run always seeds the baseline and returns zero deltas); BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxItems (default 500). Raise the cap for a bigger run; you pay per delivered row.

Q: What does watch mode remember between runs?
A: A private baseline of source-native record ids in a named key-value store. Each later run diffs the live source against it and emits only changes.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs except the watch baseline. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other IP and trademark watches actors?
A: Same output shape and billing model; this one covers www.ic.gc.ca. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (maxItems) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
• First watch run shows no deltas → expected: it seeds the baseline; changes appear from the second run.
• Residential proxy unavailable → the actor falls back to a direct request, which the source refuses → the run fails loud and bills nothing; make sure your plan includes residential proxy.

🔗 Related Actors

• Canada CIPO Trademark Decision Watch — Trademarks Opposition Board decisions published by the Canadian Intellectual Property Office: case title, neutral citation, publication date and the…
• EPO Amended Patent Specification Watch — Granted European patents narrowed or upheld after opposition or limitation (B2/B3). A litigation-relevant signal — roughly 35 a week worldwide
• EPO Patent Application Publication Watch — European patent applications as they publish (A1/A2/A3). A high-volume bulk feed — roughly 3,700 publications a week
• EPO Patent Correction Publication Watch — Corrected European patent publications (A8/A9/B8/B9). Roughly 50 a week — docketing accuracy rather than bulk
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.