It’s important to understand what David Williamson’s short book is and what it is not. It is not, and readers should not expect it to be, a complete or exhaustive guide to how to effectively critique another writer’s work. It’s clear Williamson never intended it to be that.
Instead, the book is a collection of 26 slightly revised blog posts, plus three additional articles, that provide brief discussions of some critique topics and techniques. Because the original posts—running in alphabetical order from “Appearance” to “Zaftig”—were short, Williamson could only scratch the surface, touching on a few topics each time.
In general, he does a reasonable job with the space he has available. There are a few places where his suggestions miss the mark, however. In his chapter on point of view, he seems to be OK with head-hopping, that is, shifting from one point of view character to another within a scene or chapter without any sort of break, like a scene break. This goes against the general guidance for writers that there should be only one viewpoint character per scene.
In his chapter on verb tenses, he fails to address transitions into and out of flashbacks, where the verb tense must naturally shift.
Finally, in several chapters, Williamson inserts elements of his faith. This is inappropriate in a book that has nothing to do with religion or faith.
These problems pull what would have been a 4-star rating for its target audience down a half star (although most places where this review will be posted don’t allow half-star ratings).
Elements of Critique can serve as a basic introduction to critiquing for a writer who’s just getting started at it, but it is not appropriate for a more experienced critiquer.
Kate Jonuska’s idea to create a dictionary of critique terms and intermingle them with a bit of discussion seems like a clever technique at first, but the idea quickly loses its luster. First, Jonuska interrupts the flow of the book every time she inserts the definition of a new term and provides an example or two. These interruptions make it very hard to piece together coherent concepts from which a reviewer can build a critique.
Second, dictionaries are not typically the kind of book one reads in order to try to build a broad understanding of a concept. So between the final third of the book, which is devoted to an A to Z listing of terms, their definitions, and examples, and many of the same terms, definitions, and examples spread through the first two-thirds, maybe a third of the book is devoted to discussions of techniques for providing critique. And as with a standard dictionary, if you don’t know or don’t remember the term you’re trying to get a better understanding of, scrolling through the dictionary, hoping to come across the one you’re looking for is hardly an effective way to learn.
At times, the author notes that certain concepts are known by several different names. So far, so good, but in the dictionary section, while she does point the reader to the primary term from the secondary one(s), she misses an opportunity to use internal hyperlinks to make the jump to that primary term far easier than scrolling and scrolling and scrolling forward or backward to get to its definition.
Third, Jonuska spends as much time, if not more, addressing writers as she does reviewers. This is a hard to avoid hazard of any book which means to teach writers how to critique their own or another’s work. Writers have to know the craft in order to be able to meaningfully critique someone’s writing, but a book meant for critiquers needs to address the task of critiquing more clearly and consistently than the author does.
Finally, the book is rife with spelling and coding errors. Star Wars fans will find it hard to forgive Jonuska’s consistent misspelling of Princess Leia’s name (it’s not Leah). There are also far too many instances—dozens—where the HTML coding for the text of examples is revealed (for example, * <span style=“color: #00000A”>). The failure to catch these errors suggests either simple sloppiness or a rush to publish.
The book is not completely without merit. I did encounter a few terms and concepts that were new to me, but not enough to overcome the book’s many weaknesses. For an experienced critiquer, this book might have some value when they want to refresh their memory on a particular concept—at least if they use the same terms Jonuska does. But for the new critiquer, this book is going to be far less helpful than it could have been.
Of all the books
out there on screenwriting, this on one not to waste your money on.
Because it was
published in 2003, it contains a lot of unavoidable “errors.” For example, author
Robert Pollock could not have foreseen the death of the video rental store or
the rise of video streaming or social media. We can forgive and ignore these and
other things and move on to the more serious problems with the book.
First, it’s easy
to wonder why Pollock was hired to write the book in the first place. He has
only one screenplay that was turned into a movie to his credit, a generally
panned 1981 film called “Loophole.” At the time the book was written, he was a
professor at a community college in Connecticut, and while he “had connections”
with the Hollywood film industry, they do not appear to have been deep. (In a made-for-Hollywood
irony, the book was published eight days after the author’s death.)
Second, Pollock
alternately plays to the novice screenwriter’s dream of writing the surprise
blockbuster script and then turns around and tells that novice how many scripts
fail to even get a serious reading. The latter fact is likely still true today,
so it’s disingenuous at best to then continually dangle the ideas of the
big-dollar contract the novice dreams and of having big-name stars headline his
or her movie when so few achieve those dreams.
Third, many of
Pollock’s references to movies and directors were dated even when the book came
out, going back as far as the 1940s and 1950s, while he barely mentions those
from the 1990s and early 2000s. It seems that he was less familiar with the
more recent films and directors than those of his youth.
Fourth, the
advice the author gives the reader is often so vague and generic—write a good
script, make sure there’s plenty of tension in it, get to know people in
Hollywood—that it’s useless. He even encourages the reader to write in the
active voice, but most of his own writing is passive and stiff: “one should…,”
“it is recommended that….” At other times, Pollock seems to assume the reader
knows as much about a topic as he does, which also means leaving out key
information.
Finally—and this
may not have been Pollock’s fault—the book contains intrusive little
pull-quotes throughout, with headings like “Alert!” or “Essential” or “Fact.”
By themselves, these would not have been a problem, and if done well, could
have been quite useful. But instead, they seem to have been inserted at random.
They often had little to do with the text they were inserted into, and by placing
them in the middle of a titled section, they disrupted the flow of the text
with their irrelevancy. I suspect this was a characteristic style of the
hundreds of books in the “Everything…” series (I’ve seen things like it in
other books for novices) but it was so badly done that many times it tempted me
to throw the book across the room in frustration.
Bottom line:
don’t waste your money. (I’m glad I got this book for free from a friend. And I
know now why he was getting rid of it.)
This
little book is outdated in some ways, yet it has certain charms and retains
some value.
Written
in 8 BG (“Before Google”)—that is, in 1990, when BG still referred to the
Brothers Gibb, personal computers were a new thing, and the internet was mostly
a gleam in technologists’ eyes—it’s amusing to see references to hand-written
student papers and reminders to make sure you use a new typewriter ribbon when
getting a paper ready to turn in.
It
was also clearly written primarily for college student writers facing the
near-future prospect of having to write papers for employers, not just
professors. And it relies on memorization of some rules (only a few,
mercifully) and tables and appendices in which the reader can look up
grammatical terms and irregular verb forms, because, of course, at the time
there was no Google to ask and get 3,578,227 possible answers in 0.0286 seconds.
These
quaint antiquities aside, this little book’s first five chapters, and parts of
the sixth, do have some value. For example, Chapter 1 kindly clarified for me
exactly what a comma splice is, and Chapter 2 reminded me that what I’ve been
calling a gerund (like “calling” just now) is actually a verbal, not a
verb. Well, dang!
Professors
Funk, McMahan, and Day, the authors of this little tome, are still at it. The 9th
edition of this book’s replacement is available on Amazon, but at nearly $50 a
copy, I have a hard time believing it has the same value as this one, also
available on Amazon for a mere $4.59.
This
is the last post in the series on characterization. Next time we’ll move on to
setting.
Photo by Jeroen van Oostrom, via FreeDigitalPhotos.net
If
you’ve traveled around the country, or watched TV or the movies, or done just
about anything other than live under a rock, you know that people speak
differently in different places. They have different accents, different slang
terms, and different styles of speaking. Compare the laconic Mainer or cowboy
to the fast-talking New Yorker. And that’s just in the United States!
Canadians, Britons, Scots, Irish, New Zealanders, Australians, and some Indians
and Kenyans (to name just a few) speak English, too.
And
they all do it differently.
England’s
WWII Prime Minister Sir Winston Churchill famously described America and
England as “two nations separated by a common tongue.” Love that line.
The
differences aren’t just geographic, either. There are differences between
racial and ethnic groups, economic classes, age groups, education levels, and
more.
And
we writers want to capture them. After all, the way a character speaks says a
lot about them.
But
aye, there’s the rub. Several rubs, in fact.
Hard to Replicate
Dialect
is hard to write and even harder to read and understand, especially in large
quantities. Have you ever tried to
write out a Bostonian’s accent? We all know “pahk the cah in Hahvahd Yahd,
Roberter,” right? Or that of someone from the Deep South? Y’all sho’ kin trah.
Or someone from The Bronx? Fuhgeddaboudit. You end up doing all sorts of
alphabetic gymnastics trying to capture sounds that are hard, if not impossible
to represent just with English’s 26 letters and a few punctuation marks. And
try to use all those special characters you find in dictionaries, the ones that
are supposed to help you understand how to pronounce a word? That’s asking a
reader to work way too hard. A writer might get away with that once. More than
that and the reader is likely to put the book down.
There
are better approaches. I’ll have suggestions on them later.
Disrespectful?
The
second rub is that some writers, teachers, and critics think writing in dialect
shows disrespect for characters, that it belittles them. There may be some
merit to this argument. Think about it: How many characters have you read, who
were supposed to have high cultural or economic standing, but spoke with a deep
southern accent or a slow western drawl if the story wasn’t set in one of those
locations? Not many, I’ll bet. That mismatch between how a reader expects a
character to sound and how they actually do could
make a character more interesting, but it could also be used to mark them in a
negative way.
If
a writer is creating this mismatch
intentionally, they need to make that clear as early as they can. Note,
however, that this might not be early at all if the author intends to misdirect
the reader, the other characters, or both.
Foreign
languages are also things to be careful with. If a character comes from a
foreign country, it’s OK in some circumstances for an author to drop in an occasional foreign word:
If it’s the right word, or the only word, she
can use to express a certain idea or concept;
If it’s a common-to-him word that he would
naturally use in place of the English one; or
Just to establish the character as being foreign.
It
can also be OK for an author to throw into a character’s dialogue enough
foreign words to show her putting on airs or otherwise trying to be someone she
is not.
Better
ways to show that a character is speaking English as a foreign language are to
use English words that are technically correct, or almost right, but are not
the ones a native speaker would use, or to rearrange the structure of their
sentences. Think about how Yoda spoke in the Star Wars movies, with his verbs at the end of his sentences.
Cover Other Weaknesses
A
third rub is an author using dialect, foreign words, or jargon to cover up
other weaknesses in the piece, particularly in characterization, or to show off
their own vocabulary. A friend of mine once used the word mephitic to describe
the smell of a men’s restroom. Sending readers to the dictionary is a good way
to ensure they never pick up the book or story again.
When Jargon is Acceptable
If
a character works in a field that has its own specialized jargon, which all do,
then it’s appropriate for him to use that language. Of course, the author needs
to use that jargon correctly, and in ways that would be natural for the
character. People often forget that others don’t understand their jargon, which
can lead to confusion and misunderstanding. Authors can and should take
advantage of that, so long as only the other characters are confused and not
the reader—at least not for long.
There’s
a special proviso here for non-fiction works: If the piece is being written for
a specialized audience (say for hunters and sport shooters in Guns and Ammo) or for a field’s
professional magazine (for example, Cell
in biology), then the jargon needs to be there. It adds clarity and accuracy
rather than reducing it.
The
general rule of thumb is that authors should use dialect, foreign words, and
jargon sparingly, only enough to establish what they need to about the character.
Once the character’s background, social standing, culture, heritage,
profession, etc., have been established, the author should minimize how much
they use those special words and phrases. If a character has been off-stage for
a while, using a little dialect or jargon when they come back into the story is
appropriate.
Questions for You
All
right, then, time to put on your reviewer’s hat. Here are some questions to ask
regarding dialect, foreign languages, and jargon as you review a work.
Is the dialect, foreign language, or jargon
necessary and appropriate to the piece?
If it isn’t necessary, appropriate, or both,
what should the author do to fix the problem?
Does the amount of dialect, foreign language, or
jargon, or the way it’s being written, make the piece hard to read? Does it
confuse rather than clarify?
If so, what should the author change or remove?
Does the author seem to be using dialect,
foreign language, or jargon to belittle a character?
Is that appropriate for the story? For example, does
he want the reader to not respect that character?
Could that be accomplished some other way, such
as through the character’s behavior? Is that being done already?
If none of these are the case, what should the
author do to fix the problem?
Does the author seem to be using dialect,
foreign language, or jargon to cover up other weaknesses or over-impress with her
vocabulary?
Used
properly, dialect, foreign words, or jargon can add to a piece, giving it the
flavor of a particular environment, giving a character an added or necessary
dimension, or adding a degree of authenticity or authority to the story. That’s
what you, as a reviewer, should be trying to help the author achieve.
What
do you look for, and look out for, when reviewing how an author uses dialect,
foreign terms, or jargon? Y’all kin ‘splain yore thinkin’ in that comment box
down yonder.
Comedy has been defined as “ordinary people in extraordinary situations, or extraordinary people in ordinary situations.” But what if the piece you’re critiquing isn’t comedy—or isn’t meant to be comedy? When a character you’ve come to know suddenly acts in a way that makes you stop, scratch your head, and say “huh?”, maybe there’s a problem.
Maybe. That’s an important word. What does the story’s context tell you about this new behavior? If Alice suddenly starts screaming, which she’s never done before, but it’s because the car she’s riding in just went off a cliff, that’s reasonable. If, on the other hand, as the car begins its graceful, 1,000 foot descent, she calmly takes out her .357 Magnum and blows away the driver, well, maybe not so much. OK, I can understand her being pissed at him, but really, what good does shooting him now do? [Oh, right. Next, she unbuckles her seat belt, pulls her parachute from the back seat, wrestles it on—how convenient that all the straps are already adjusted to her size—opens the door, steps out, and— SPLAT! Oops, too late! Dang. Well, BASE jumping [1] was never her forte, anyway.]
What’s the Reason?
There are lots of stories in which someone’s personality changes suddenly and dramatically, but the good ones (and some of the not-so-good ones) justify the change. You know why. And if the change makes sense, all’s well.
It is possible for an author to have a character’s behavior change significantly, or have some new and very different-from-the-norm trait appear, without explaining it or setting the context for it before or at the moment of change. If he does, though, he’s asking the reader to trust that all will be made clear in good time. That’s fine, so long as he keeps that implicit promise.
Sometimes it can be hard to tell if the promise is kept, however. If you’re reading a long piece like a novella or full-length novel, but you’re only seeing it a few chapters at a time, the explanation for the new behavior may not show up in the material you’re reading. In that case, you need to ask about it. If it’s a mistake, it’s possible the author didn’t realize she’d made it.
Questions For You
Your task as a reviewer, then, is to do a kind of sanity check on any sudden change or new behavior. Here are a few questions to ask.
Have the character’s circumstances changed suddenly, requiring a behavior she hasn’t demonstrated before?
If there was not a sudden change, but a more gradual one, has the author prepared me for this character’s new behavior by establishing the circumstances that warrant it?
Has the author hinted that there might be more going on with this character than meets the eye?
If she did, how? Why did this effort work?
If the answer to any of these questions was no, what was missing?
Whether the circumstances changed slowly or suddenly, does the new behavior make sense?
If not, why not?
Do you need more information for the behavior to make sense? If so, what?
Has the character demonstrated the ability to change in the past, or is this change forced on them?
If it was forced, what is the effect of that?
If you’re not clear on why the character’s behavior has changed, you’ll want to bookmark the moment the new behavior appears and watch for the explanation to be revealed. If it isn’t, this is something you’ll want to flag for the author.
What else do you look for when watching for out-of-character behavior? Please add your suggestions in the comment box below.
[1] BASE jumping is an extreme form of sport parachuting. BASE stands for Buildings, Aerials (or Antennas but definitely NOT Automobiles, falling or otherwise), Spans (e.g. bridges), and Earth (e.g. cliffs).
One of the things writer Anne Lamott is famous for is her advice, “Give yourself permission to write a shitty first draft.” To me that’s a kind of liberation theology for writers, but that’s a subject for another time. Today I’m going to continue to pull back the curtain on my writing process, at least as it relates to getting all the scenes in order for the second draft of this book.
So: “Give yourself permission….” Done.
“Write a shitty first draft.” Done.
OK, maybe “shitty” is a relative term, but while my read-through of the first draft got a “not bad” rating, as I wrote last time there were problems with the timeline, that is, the sequence of events in the plot. Timeline is especially critical for this book for two reasons.
One, it needs to end at a certain time of year in order to take advantage of certain weather phenomena in Dallas.
One-a, there are other events in the book that take place outdoors. They needed to fall at times of the year when they could take place outdoors or something would have to change.
Two, this book, like its predecessors The Eternity Plague and Chrysalis, has five–count ’em, five–interconnected story lines happening at once, so the sequencing of the events in each story line needs to be right.
Since I knew I had problems, and on top of that I had about 50 scenes that weren’t organized into chapters, I had two tasks that needed to happen pretty much in parallel: figure out the overall timeline and get those scenes into chapters. Then I could look for the scenes I already knew were out of order and identify where they should have gone.
Because I’m a “plotter”–that is, I work from an outline–building an updated outline of the story would take care of those tasks. I do this using Microsoft Excel. Yes, the spreadsheet program. I have a column for the chapter and scene number, a column for each major and key minor character, and a column for the timeline. With Excel, I can have as many columns as I want and not have to worry about trying to fit them all into one page, even in landscape format, which is what I’d have to do if I tried to use a Word table.
Since there are five major characters–Janet Hogan, the protagonist; Lisa Lange; Sarah Green-Dale; Reverend Will Baxter; and Lew Crandall–that’s where the spreadsheet started. Then I added the key minor characters associated with them, plus one for “Others.” To make them easier to see, I color coded the cells on the spreadsheet row with the characters’ names: pink for Janet and her crew, red for Lisa and her crew, etc.
Instead of one chapter/scene column, I put two in this time: one for where each scene fell in draft 1 and the other for where they needed to go in draft 2. Next, I added one column for how each scene related in time to the one before it, and one more for what calendar month and year that scene fell in.
Then, on the row for each scene, I wrote a brief description of what happened in the scene in the column or columns for the characters involved.
The end result: 18 columns by 142 rows! In other words, this, taped up on my guest bedroom wall:
Yikes. That’s three landscape-format pages wide by 10 pages tall! It’s so big, I had to split it into two 3-pages-wide by 5-pages-tall sets. This technique is NOT for everyone!
Before I printed this monster out, I did that sorting of which scene needed to go where. Here’s an example from the beginning of the novel.
Outlined in blue, you can see how I planned to bring three scenes from chapter 2 forward into chapter 1.
I also worked out the timing. Here’s the timeline for those same scenes.
But aren’t those August 26th scenes out of order? Well, by strict definition, yes, but hey, I’m a writer–I can finesse that! “Two weeks earlier…”
Great! Now I had a plan and could start editing.
But of course, no plan survives first contact with reality, and that’s what happened today. I was chugging along, working on what was supposed to be scenes 7 and 8 of chapter 1 when I discovered that they needed to go before the three scenes I’d pulled in from chapter 2, not after! D’oh! OK, that’s an easy fix.
These are some of the reasons why the first draft of a novel should NEVER be the final draft.
Last night I finished my first complete read-through of the first draft of book #3 (working title, Guardians, although I’m considering Wild Spread as an alternative). (No, that’s not me over there on the right. My ideal reader, maybe. At least her interest level looks right.) I’ve got almost 10 pages of hand-written notes of things to check, fix, delete, etc.
Overall verdict: not bad.
There are some scenes that are way out of position. There’s a place where one of my secondary characters chrysalizes, then a few chapters later appears again in her unchanged, original form, as if the chrysalization never happened. Oops. Well, that’s the sort of thing that happens in a first draft. The fix should be easy: delete the sentence that reports the chrysalization. I can still end that scene in a way that will make readers want to find out whether what Amanda fears will happen to her or not. (Hint: it–NO, I’m not telling!)
My barber asked me yesterday if I ever forget what I’d written earlier in the draft. Heck, yeah! Happens all the time. Having an outline helps but there are always details about something I wrote months ago that get forgotten or contradicted later. Maybe other writers can keep all of that straight but in a 110,000+ word draft, written over the course of six or seven months, for me, fuhgeddaboudit.
This is just one reason why first drafts should never ever be final drafts!
I still need to go though the draft and sort out the timeline. That’s especially important this time because the final scene has to take place in May or June. And since the book opens at a specific time of year, right after the end of Chrysalis, everything else needs to happen at the right time or the last scene could end up in some other month, when the weather pattern that’s critical to the end of the story doesn’t happen, or doesn’t happen so much, in Dallas. (That’s a teaser.)
I’m actually looking forward to getting started on Draft 2. I know lots of writers who dislike, hate, despise, you pick the negative verb, revising. Not me. I enjoy it. While it’s a different kind of process, and takes a different kind of creativity than writing that first draft is/does, seeing the work get better is a reward in itself. I get a real feeling of satisfaction at the end of a day of editing when I know the story is better than it was before I started.
Draft 2 is what my writers’ group will get. (Get ready, guys and gals. When it starts to come your way, it’s going to come in big chunks!) Their feedback will help me create Draft 3, which is what I plan to send to my still-to-be-selected editor and beta readers. Draft 4, created from their feedback, should be what goes to CreateSpace and Smashwords to be published.
When will that be? I don’t know. I’d hoped to get this book done and out by the end of this year, but I don’t see that happening now. If nothing else, since I don’t know who’s going to edit the book, I don’t know what his or her timeline will be: when they’ll be able to take it, how long they’ll need, etc. All in good time. Things are moving forward, and that’s what matters.
The Cochise Writers’ Group, which I co-founded with Cappy Hanson, has gone through phases of growth and contraction, as every group does. We’ve been as small as four members, and as large as 17! We hit that number about a year ago and it became obvious very quickly that if we didn’t do something, the group was going to be unmanageable. The first thing we did was close the group to new members.
Our only saving grace was that not everyone in the group was submitting work. A lot of the new members did initially, in that burst of enthusiasm that comes with being new at something, but that tapered off over the months. Now we’ve got about half a dozen members who submit work more or less regularly, and that makes things easier to handle, both from a critique standpoint and from a management one.
But as the months went by, it became clear to us that some of our longer-term members weren’t actually contributing much. Their attendance was spotty, they only provided critiques once in a while, and they weren’t submitting work. Something had to change.
Now, we’d been pretty tolerant with these folks. Some had been regulars at our every-two-weeks meetings, and had contributed work in the past. But now they were dealing with medical issues, either their own or their aging parents’, or there were work issues, or other things, and for the sake of keeping them engaged in the writing process, at least a little, we’d let them remain members. That was fine while those problems were active, but as they resolved themselves, these “writers” now weren’t living up to the expectations document we’d put together over the summer.
So Cappy and I looked over our membership list just after Christmas and picked out half a dozen people whom we felt we needed to say, “Time to fish or cut bait.” We each took three and either talked to them in person or over the phone. No e-mails; this all had to be personal.
The message was this: You have until the end of March to do the following, or we’re going to have to ask you to leave. (1) Start attending regularly, even if that’s only at one of our two locations. (We meet in two different towns, Sierra Vista and Bisbee, which are about 30 road miles apart. Some of us drive 60 miles or more, round trip, to get to our meetings. This wouldn’t be acceptable, or even necessary, in a big city. In a rural area, it’s just the way things are.)
(2) Start critiquing everything the other members send out. If you have to send your critiques back via e-mail, that’s fine. If you have to give them to one of the members who goes to all meetings so they can deliver them in person two weeks later, that’s fine. But do the work.
(3) Start submitting, or at least participate in the Google Docs spreadsheet one of us created to record your daily word count, how much time you spent working, or whatever. In other words, we’re a working writers’ group: prove to us that you’re writing.
That got some of the people to step up. Some took that necessary deep breath and made their first submission. Others, however, did little or nothing.
And so, on Tuesday night, Cappy and I took the first of those people aside and gave her the news: we were asking her to leave the group.
This is never easy. We’ve only had to do it once before. The truth is, though, that besides actual writers, critique groups attract other people: wannabes, dreamers, procrastinators, lookie-loos, groupies, people looking for some kind of social contact. Dead weight, in other words, for a working group. Those people have to be identified, given a chance to change, and if they fail or refuse, let go.
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
X Pixel enables businesses to track user interactions and optimize ad performance on the X platform effectively.
This cookie is set by X to identify and track the website visitor. Registers if a users is signed in the X platform and collects information about ad preferences.
2 years
personalization_id
Unique value with which users can be identified by X. Collected information is used to be personalize X services, including X trends, stories, ads and suggestions.
2 years
external_referer
Our Website uses X buttons to allow our visitors to follow our promotional X feeds, and sometimes embed feeds on our Website.