--- name: log-twitter-affiliate-marketing description: "Affiliate marketing through your DMs. A log play (docs/useCases/twitter/affiliateMarketing.md): You use a tool, you make content about it, and people message you about it. This page turns those conversations into affiliate income without sounding like a pitch: each person gets a reply about their own thread, an update on what you've built, and the tool with your affiliate credit only where it actually helps them. The other side of the page is the tool companies themselves: getting onto their partner, referral or creator program and booking the call." when_to_use: "Use when the owner asks for this, in words like: \"answer the people asking about in my dms with my affiliate link\", \"turn the dms about into affiliate money\", \"follow up everyone who asked about the tool\", \"get me onto 's affiliate program and book the call\"." metadata: summary: "Affiliate marketing through your DMs" --- # Affiliate marketing through your DMs This is the log play `twitter/affiliateMarketing`. Before anything else, call the log MCP tool `getGuide({ useCase: "twitter/affiliateMarketing" })`: it returns this page and makes it the session's play, so every log tool's answer says which step you are on and a send with no play loaded is refused (rules 157, 158). Then follow the steps in order. Draft every message from that person's own thread and the owner's real replies (`voice` with no text, `search`), never from memory, and never send two that read alike (`sameAsSent`). You use a tool, you make content about it, and people message you about it. This page turns those conversations into affiliate income without sounding like a pitch: each person gets a reply about their own thread, an update on what you've built, and the tool with your affiliate credit only where it actually helps them. The other side of the page is the tool companies themselves: getting onto their partner, referral or creator program and booking the call. Inbound and outbound are on other pages: [dmInbox.md](../log-twitter-dm-inbox/SKILL.md) reads who is waiting, [engagerDms.md](../log-twitter-engager-dms/SKILL.md) opens new conversations. How the owner asks for it: "answer the people asking about in my dms with my affiliate link", "turn the dms about into affiliate money", "follow up everyone who asked about the tool", "get me onto 's affiliate program and book the call". ## Run it from a fresh context Say: **"go on docs/useCases/twitter/affiliateMarketing.md for ``, link ``"**. The agent then reads this page and [README.md](https://github.com/matthewdonsemail-lab/log/blob/main/docs/useCases/twitter/README.md) and runs the steps. ## The steps | # | Step | Tool | Done when | | --- | --- | --- | --- | | 0 | Session check | `twitterSessionCheck` | `loggedIn` | | 1 | Read every conversation, X Chat included, and index it | `searchIndex` { account } (`log search index`) | "N conversations, M messages" and the chunk count | | 2 | Find the conversations worth a follow-up: anyone who asked about the tool, offered work, a call or a collaboration, or went quiet on an open thread | `search` { query: " enrichment", with, after } (several queries: the tool, "call", "consulting", "affiliate", "role") | a short list of people and conversation ids | | 3 | Read each person's whole history before writing a word: the old DM thread and the X Chat thread merged into one timeline | `twitterDms` { account, with: "" } | you know the last thing each side said, and what was promised | | 4 | Sort them: **owes you an answer**, **you owe them something** (a doc, a look, a reply), **left hanging**, **competitor** (building a rival tool), **tool company** (their partner program) | a table for the owner | the owner agrees the list | | 5 | Write one message per person: pick up exactly where the thread left off, one line on what you've built since, then the offer framed as something for them. The link goes only to people who don't use the tool yet, and never to a rival's founder | house style | the owner approves each line | | 6 | Tool companies: ask for the partner, referral or creator program, show the reach (views, who follows you), and offer two concrete call times in their mornings or a calendar link | `twitterDm` / `twitterDmLive` | a time agreed | | 7 | Send, dry run first. Two or more people go through the queue as dms | `twitterDm` then `twitterDmLive` { userId, text, approvedBy, confirmLive }, or the README queue with `action: "dm"` | X's answer is `sent` | | 8 | Watch for replies. The inbox hook flags a new message with its text, X Chat included | the inbox watcher (agent hooks) | each reply read with `twitterDms` { with } before answering | ## What a message looks like > hey `@someone` sorry this slipped past me. since we spoke i've been building `` all in public ``. you were asking about `` so this might help, `` gives you `` free here `` > hey `` the referral route works for me and i'm keen to hop on a call and plan it out. would `` or `` at `