Including a Doc within a Doc is a quick and simple way to repurpose content and create new Docs from your existing materials. Whether you're putting together a tailored sales kit or compiling specific resources for a particular customer, this is a great feature to have on your radar.
The following 2-minute video covers:
Explanation of a nested Doc
Explanation of a wrapper Doc
The multiple benefits of repurposing content
How to add in a nested Doc into wrapper Doc
How to check the nested Doc was copied over correctly
How to measure the performance of a nested Doc
How does it work?
While editing a Turtl Doc, click the three dots on a Surf page thumbnail and select 'Include Doc.' Enter the URL of the Doc you want to embed and click 'Include.' The complete Doc will be placed right after the currently selected Surf page thumbnail.
The nested Doc appears as one page in your Surf page timeline, but all of the embedded Doc pages are accounted for in your page count.
What happens when you edit or update a nested Doc?
Any changes you make to a Turtl Doc will automatically update everywhere that Doc is used - including if it's embedded into another Doc.
This means that you can have different users working on different parts of one Doc. In technical terms, the "wrapper" Doc (the main Doc) calls upon the "module" Doc (the nested Doc), meaning that Docs can be updated separately and then tied together.
Company A wants to make a thought leadership Doc:
They hire Agency X to complete one part
They hire Agency Y to complete another part
Like this, Company A can create two workspaces and give Agency X access to one and Agency Y to the other. The agencies can build two separate Docs in the same style, and Company A can then combine them in one wrapper Doc.
So it’s one Doc within another Doc - but what happens to analytics?
Because a Doc can be viewed either independently or embedded in another Doc, we collect analytics both in the embedded Doc and the wrapper Doc.
This means that the total reads on a Doc are a combination of those it receives as a separate piece of content and those it receives as part of another Doc.
The wrapper Doc will collect analytics as a whole, so its analytics data will include analytics events that happened both on the wrapper doc and any nested docs it contains.